App developers in St. Louis for mobile app development

React Native is a practical choice for apps built around accounts, forms, bookings, payments or content. We usually use it to share a codebase across iOS and Android, adding native modules where a feature needs them. That gives you shared code to maintain while still rendering each platform’s interface components. If the app needs deep device features, we go native instead.

A progressive web app is another option for a staff tool. It skips store review, but it will not appear in the app stores unless packaged for them. On an iPhone, it can ask to send notifications only after someone adds it to the Home Screen. Think about how your staff will find and open the tool before choosing that route.

We start by learning about your business, audience and goals, then agree the scope with you. That gives us a basis for choosing the platform around the features people will actually use.

For a state or local government app, we design and check mobile screens against WCAG 2.1 Level AA, the standard required by the ADA Title II rule. Agreeing the screen flows early gives us a basis for applying that standard across the app.

For checkout, the item being sold determines the payment setup. We set up store billing for eligible digital content and subscriptions, and a separate payment gateway for physical goods or services. Businesses in the United States can sign up to accept payments with Stripe.

Gather these details so we can discuss the scope and the work behind each screen.

• Developer accountsStart registering Apple and Google accounts in your company’s name; organisation verification needs a D-U-N-S number.
• Existing systemsList your website, booking software, CRM and payment provider, their APIs and who has admin access.
• Privacy policyPrepare a policy that matches the data the app collects, for its listing and the app itself.
• Account deletionIf people can create accounts, plan how they will start deleting them inside the app.
• First-release measurementDecide which screens and drop-offs you want to understand through analytics and crash reporting.

• !

  Wrapping a website in an app shell

  Give people a reason to install the app. A repackaged site risks rejection under Apple’s guidelines.

• !

  Demanding sign-up immediately

  Let people see useful content before creating an account when significant account-based features are not needed.

• !

  Asking for notification permission at first launch

  Ask when the benefit is clear, such as after an order. On Android 13 and later, notifications stay off until the user permits them.