Mobile App Development in St. Louis: A Storyboard for the Moment an App Asks Where You Are

Updated November 2026 · Written and maintained by the Progression Agency strategy team

The system prompt appears and asks to use your location. Most people decide in a second. Mobile app development in St. Louis has reason to get that second right: NGA’s western headquarters opened here in 2025 and the city’s geospatial work is a real local industry, so location is often the product and not a side feature. This page storyboards the permission flow frame by frame: what comes before the prompt, what the prompt says, what happens on no, and what Apple, Android and the FTC expect. It is for product owners and founders. Progression is based in New York and works with St. Louis teams remotely, with on-site sessions on request.

A blank system prompt

The card shows the moment this page is about: a system dialog, a map behind it and no hint about why. Everything that follows is what could have come before and after it.

The six frames are not a style guide. They are a checklist for one decision, and each frame can be tested by someone who has never seen the code. Product owners and founders can use them to brief a designer, to review a store submission or to compare quotes from different firms.

A product owner sees a permission. A user sees a stranger asking where they are. The storyboard below walks six frames that make the second view friendlier without hiding anything.

Mobile app development in St. Louis, where location is the product

The Missouri Partnership reported on October 1, 2025 that Next NGA West, the National Geospatial-Intelligence Agency’s $1.7 billion western regional headquarters, had officially opened in St. Louis, and called it the largest single federal investment in St. Louis history. Taylor Geospatial says on its own site that it is building the open infrastructure needed for GeoAI to scale globally, and describes itself as a nonprofit that strengthens innovation capacity in the St. Louis region.

No claim is made here about any contract with NGA or any relationship with Taylor Geospatial. The point is narrower: in a region with that much geospatial activity, founders and product owners are likelier to build apps in which location is the product. Logistics, utilities, public safety, retail and field service all fit.

Frame 1: before the prompt

A short screen says what the app will do with location and why now. It appears the first time a feature needs it, not at launch.

• Name the feature that needs location, in the user’s words.
• Say what the app will not do, such as sharing location with advertisers, if it is true.
• Offer a way to skip without losing the rest of the app.
• Hold the system prompt until the person taps continue.

When in the flow should an app ask?

When a person first taps something that cannot work without it. Asking at install or launch trades trust for a few extra taps saved.

Frame 2: what the prompt says

The system prompt carries a purpose string written by the app’s developers. Apple’s App Store Review Guideline 5.1.5 says to use Location Services only when directly relevant to the features and services the app provides, and to notify and obtain consent before collecting, transmitting or using location data.

Why not ask at launch?

At launch the person has not yet seen a reason. A request tied to a tapped feature has a visible cause, and refusal costs less because only that feature is affected.

Frame 3: foreground or background

Android’s location permission documentation describes each permission by a category, foreground or background location, and by an accuracy. A feature that shares location once or for a limited time needs foreground access. A feature that constantly shares location or uses geofencing needs background access.

Ask for background only when a feature cannot work without it, and explain the reason in the screen before the prompt. Many apps can do their job with foreground location and an optional later upgrade.

Frame 4: precise or approximate

The second characteristic is accuracy. Precise location can show an exact spot, and approximate location shows a general area. Match the request to the feature.

• Turn by turn directions and delivery tracking need precise.
• Weather, local news and neighborhood search work with approximate.
• Offer the choice on first use and respect it afterward.
• Test every screen with approximate turned on.

Does approximate location hurt the feature?

Sometimes. Directions and delivery tracking suffer, while search and weather do not. Name the features in the storyboard and mark which accuracy each needs.

Frame 5: the user says no

A refusal is a normal answer. An app that handles it well keeps the person, and an app that hides behind a locked screen loses them.

Frame 6: what happens to the data

The last frame is about what the app does with the location it collected. The FTC’s January 2024 order prohibits data broker X-Mode Social and its successor Outlogic from sharing or selling sensitive location data, in what the agency described as its first settlement with a data broker concerning sensitive location information. The FTC charged that it failed to obtain informed consumer consent.

In plain words: do not sell or pass on raw location without consent, state how long you keep it, and make the screen match the system. Ask your counsel how your own retention and sharing should be worded.

How long should location data be kept?

As short a time as the feature allows, and the period shown to the user must be the period the system applies. Ask counsel about retention for your product.

Who writes the words on each frame?

Three people touch the text: the product owner who knows what the feature does, the designer who fits it on a screen and counsel who checks the promise. Name them before the first draft.

• The product owner writes the plain purpose sentence.
• The designer fits it to the dialog and the screen before it.
• Counsel checks any sentence about sharing, selling or retention.
• Engineering confirms the system does what the sentence says.
• One person owns the final text and keeps its history.
• Translations are checked by a speaker, not a tool alone.

How do you test a permission flow?

The flow needs its own test plan, because each choice branches into a different app state. A short checklist covers the usual cases.

1. Install fresh and trigger the feature.
2. Allow while using, then use the feature.
3. Reset, then choose approximate.
4. Reset, then refuse, and walk every screen.
5. Change the setting later and relaunch.
6. Check that the data screen matches what the system stores.

• Run the plan on at least two phones for each platform.
• Repeat after every release that touches location code.
• Keep screenshots of each branch with the build number.

What a location app costs

Mobile app development in St. Louis is priced like mobile app development elsewhere, with no local premium. App development in St. Louis for location products adds GIS engineering as a scope line, and mapping and data licenses are priced by their vendors.

Bands by app complexity

Each row runs from the typical low to the published high in the US market for that kind of app.

What moves a location app between bands

Background location, real-time tracking, offline maps, many user roles and privacy review each add time. A product that asks for foreground location once and shows a map sits near the lower band.

• Background tracking and geofences.
• Offline maps and caching.
• Several roles with different views of the same data.
• Integrations with dispatch, field service or fleet systems.
• A privacy review with counsel before launch.

For a broader picture of app pricing, see our app development cost page. For marketing in the same city, see our marketing agency in St. Louis page.

Related services and guides

Pages that sit beside this one:

• App development agency
• App development cost
• Software development company
• Marketing agency in St. Louis

Frequently asked questions