On November 5, 2026, Google published a short tutorial showing how to photograph a sketch, upload it to Gemini, select Canvas and ask it to code an app. Users can then test the preview and request changes. This is guidance for a Canvas workflow, not an announcement of a new model. Official source.
Make the sketch describe behavior, not just appearance
For a habit tracker or small game, a drawing communicates layout but may omit what buttons do, how invalid input is handled or whether changes survive a reload. Our recommendation is to add a short behavior brief alongside the image. That makes the preview easier to evaluate and helps avoid repeatedly correcting assumptions.
A proposed acceptance check
- Label inputs, buttons and expected results in the sketch; specify what should happen after each action.
- Try the main path and one failure case in the preview. For a tracker, add an item, change its status and test empty input.
- Reload and check the narrow-screen layout. Ask where data is stored and what sharing exposes before inviting other people to use the prototype.
What the tutorial does not confirm
The short announcement does not provide a complete plan, region, quota or deployment matrix. Check Canvas help and the options actually available in your account. A successful preview does not by itself verify secure storage, access control or production readiness. The validation checklist above has not been executed by this site. Google’s Canvas help also warns that anyone with an app’s public link can view and edit its associated data. Use sample data when evaluating public sharing.
Sources and method
Official source · Related documentation
Prepared with AI assistance from official materials, checked on November 6, 2026. No hands-on test was performed. The checks suggested above are editorial recommendations.
