We build Herd Advisor (package com.herdadvisormobile, “Herd Advisor: Cattle Records” on Google Play), a cattle record-keeping app in production since March 2026 with paid subscribers across working ranches.
Our core voice use case is a strong fit for AppFunctions: ranchers frequently need to capture records at moments when both hands are occupied - working cattle chute-side, pulling a calf, driving a feed truck. Speaking “record that cow 42 got a blackleg vaccine” to Gemini and having it land as a structured record is the difference between data captured and data lost. It is also a meaningful accessibility story for field workers who cannot touch a screen for much of the workday.
We previously shipped this as a Google Assistant App Action (custom intent custom.actions.intent.CATTLE_RECORD) and lost the integration in the Gemini transition. We have since implemented an AppFunction, recordCattleEvent, using androidx.appfunctions 1.0.0-alpha10 with the AppFunctionServiceEntryPoint pattern, wired to the same production transcript-processing API - implemented and compiling today, ready to test end to end.
We submitted the EAP registration form (goo.gle/eap-af) on 2026-07-30, and filed an EAP consideration request on the AppFunctions Issue Tracker component the same day.
Two asks: (1) is there anything beyond the form we can do to be considered for the EAP, and (2) is there any public guidance on the timeline for custom (app-defined) functions becoming invocable from Gemini?