twimco.Let’s talk ↗︎
Menu
Field notes / Product & engineering

Google Maps now works in AI Studio without a credit card. Here's the path from demo key to a map app your team relies on

You can now describe a route planner or store finder to Google AI Studio and get a working map in the preview, with no billing account. That makes the first version almost free. Getting from that preview to something a dispatcher uses every morning takes a few deliberate steps.

Editorial engraving of a sunny van depot where a dispatcher compares a tablet with a paper map pinned to a van as a technician loads a tool bag.

Since November 9, 2026, Google AI Studio can build apps with Google Maps Platform using a Maps Demo Key: no credit card, 100 calls a day per API, and most APIs except Route Optimization, Solar and Nav Connect. To go to production you link a Cloud Billing account (the key keeps working), and Google positions standard keys with HTTP referrer, IP or app restrictions for production web and mobile apps. Use the demo to test the idea with real users, then plan billing, key restrictions, missing APIs and the mobile app separately.

What Google opened on November 9

Google announced on November 9 that you can build apps with Google Maps Platform inside Google AI Studio. You describe what you want, say "a route planner for our van crews" or "a store finder with opening hours", and AI Studio writes the app, sets up Maps for you and shows a live, working map in the preview.

The part that changes who can try this is the Maps Demo Key. AI Studio provisions it automatically, with no credit card and no trip to the Google Cloud console. It stores the key in the app's secrets settings so you never paste it into code. Google's gallery includes examples worth looking at: a store locator using the Places API, and a route optimizer for a mobile pet-grooming fleet that uses the Routes API and accounts for fixed appointment times, priority stops and driver shift limits.

For anyone who has spent a week getting a Maps billing project approved just to test an idea, that's a real change. It also means the person with the idea, often an operations lead rather than a developer, can now build the first version themselves.

What the demo key covers, and what it doesn't

The limits are published and sensible for a prototype.

  • Quota: 100 calls a day per API, resetting every 24 hours. Enough for a few people to click around. Not enough for a team using it all day.
  • APIs: new users get almost the whole portfolio, except Route Optimization, Solar and Nav Connect. If you already use Google Cloud and choose the free demo route, you get a smaller subset, and the Places API comes without user-generated content such as photos and reviews.
  • Terms: demo keys are governed by the Maps Demo Project Terms of Service, and Google lists their intended use as prototyping, testing and AI Studio web apps.

Two of those matter more than they look. The pet-grooming example uses the Routes API with appointment and shift logic built around it, which is fine for a demo. If your real problem is assigning dozens of jobs across a fleet, the dedicated Route Optimization API isn't in the demo at all. And a store finder without reviews or photos may test differently with customers than the real thing.

Know the two errors you'll meet. When the daily quota runs out, requests fail with a quota error such as RESOURCE_EXHAUSTED until the reset. If you're an existing Cloud user on the demo subset and the app calls an API outside it, you'll see a key restriction error, such as ApiTargetBlockedMapError in the Maps JavaScript API. Neither means the app is broken. Both mean the prototype has reached the edge of what the demo is for.

Decision guide

What the demo gives you, and what production needs

ConsiderationMaps Demo Key in AI StudioProduction app
Cost and billingNo credit card; 100 calls a day per API, reset every 24 hoursLinked Cloud Billing account, standard pricing and quotas
APIsMost of the portfolio; not Route Optimization, Solar or Nav ConnectAll Maps Platform products
Key handlingStored for you in the app's secrets settingsStandard key with HTTP referrer, IP or app restrictions
Intended usePrototyping, testing and AI Studio web apps, under the Maps Demo Project termsProduction web and mobile apps
Source: Google Maps Platform in AI Studio documentation, read November 10, 2026.
The demo answers whether the idea is worth building. It doesn't answer whether the app is ready for a Monday morning.

Use the demo for what it's good at

The demo is a superb way to answer one question cheaply: will the people who'd use this actually use it?

Put ten real jobs from last week into a route board. Show it to the dispatcher and two drivers. Watch what they look at and what they ignore. You'll learn more about the app from an hour of that than from a month of specification meetings, and our note on riding along for a shift before designing a field app explains why.

Keep the scope honest. Our earlier note on adding location only when it answers something still applies. A map that looks impressive in a preview but doesn't change a decision isn't worth taking further.

Write down what the test showed before anyone gets attached to the prototype: which screens people used, which they skipped, and which question the map answered faster than the old way. That list becomes the brief for the real build.

The demo answers whether the idea is worth building. It doesn't answer whether the app is ready for a Monday morning.

Steps from demo key to production

When the idea survives contact with real users, plan the move deliberately.

  1. Link billing. Google's path to production is linking a Cloud Billing account to the project. Your existing demo key keeps working, so the app code doesn't need to change. Set a budget alert at the same time.
  2. Restrict the key. Google positions standard keys with custom HTTP referrer, IP or app restrictions for production web and mobile apps. A key that only works from your domain or your app is much harder to misuse.
  3. Check for missing APIs. If the prototype was working around something, such as optimizing a whole day's routes, decide now whether you need Route Optimization or another API the demo didn't include, and test it on real volumes.
  4. Read the terms you're moving to. Demo keys and standard keys run under different terms. Read the standard Google Maps Platform terms before you design features around stored or cached place data.
  5. Decide who owns the code. AI Studio wrote the first version. Someone now has to maintain it, review changes and answer when it breaks.

The mobile app is a separate decision

AI Studio builds web apps. That's often right for a dispatcher at a desk. For drivers, technicians and inspectors in the field, a phone app usually earns its keep: it works with patchy signal, uses the phone's location properly, handles sign-in per worker and can capture photos and signatures on the job.

You don't need to decide this on day one. Use the web prototype to settle what the app should do. Then build the parts that live in someone's pocket as a proper mobile app, using what you learned, rather than stretching a demo into something it was never meant to be.

Watch the cost shape, too. A map that a few office staff load a few times a day costs very little. A driver app that refreshes routes and places every minute across a fleet is a different budget, and it's worth estimating before launch rather than discovering on the first invoice.

If you've built something promising in AI Studio and want help turning it into a reliable field or customer app, that's what our mobile application development team does. Get in touch.

Related work: Spin:Market

Sequence of work

From prompt to the dispatcher's desk

  1. Day 1

    Describe the route board in AI Studio; load ten real jobs from last week.

  2. Week 1

    Dispatcher and two drivers use it on paper-backed days; note what they ignore.

  3. Week 2

    Link billing, add key restrictions and a budget alert; decide on Route Optimization.

  4. Month 2

    Build the driver side as a proper mobile app with offline use and sign-in.

Illustrative plan for a small field-service team; timings will vary.
twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Spin:Market ↗︎