Google expanded Gemini Omni 1.1 Flash video generation on August 27, 2026, with developer access and new controls in Flow. The useful question for a production team is whether those controls reduce the number of revisions needed to deliver a coherent shot, rather than whether an isolated sample looks impressive.
Plan the shot around references and duration
The developer announcement describes first- and last-frame control and extensions in ten-second increments up to forty seconds. Flow's update adds creative controls around shot endpoints and output options. These features make it possible to specify more of a transition before generation, instead of describing the entire result only in prose.
Use endpoint references as acceptance criteria. A product shot may need a readable label at the end; a scene transition may need a particular framing so the next clip can begin cleanly. Check intermediate frames as well. Matching the endpoints does not ensure that an object maintains its shape, that movement follows a plausible path, or that text stays correct throughout the clip.
Separate exploration from delivery
Google describes lower-resolution draft generation alongside higher-resolution exports and upscaling options. A draft can answer composition and motion questions cheaply, while a delivery output needs its own inspection. Upscaling is an output stage, not proof that the original scene contains the desired detail.
A practical revision process holds the brief and references steady while varying one creative decision at a time. Record whether a rejection concerned movement, identity, typography or framing. Otherwise, a team can spend its iteration budget changing prompts without learning which constraint caused the failed shot.
Developer access and Flow serve different workflows
A creative team working interactively can use Flow to review and adjust material. A developer integrating generation into an application must additionally handle task status, retries, output storage and user approval. Product availability alone does not settle those implementation responsibilities.
Choose the access route based on where the reviewer works and how the result will be reused. Automation is useful for repeated briefs with clear acceptance rules. For an exploratory campaign, the extra machinery of an application integration may provide less value than a shorter human review loop.
Judge the release with a complete edit
Test a short sequence that includes the difficult transition your team actually needs, then place the generated clip into its intended edit. Compare continuity, audio alignment where relevant, readable brand elements and the time required to make a usable revision. Keep the result separate from vendor examples; Nerova has not independently benchmarked this release.
Before commercial delivery, review the terms applicable to the chosen service and the rights to supplied references. A technically convincing video is not a substitute for that review, and a new generation control does not resolve ownership of the inputs.