What business app development includes
An app is more than screens on a phone. To work, it needs several components:
- the iOS and Android app itself, which people install from the App Store and Google Play;
- a backend that stores users, orders, rewards, and settings;
- data sync with your website, CRM, accounting system, and warehouse;
- an admin panel where a manager can update banners, promotions, and notification copy without a developer;
- analytics that show what people do in the app and where they abandon purchases.
If some of this already exists, such as an ecommerce store with an API, the app can connect to your existing data instead of duplicating the catalog.
Who really needs an app and who doesn't
An app pays off where people come back often. Typical examples: food and grocery delivery, cosmetics and pet supplies bought monthly on repeat, coffee shops and salons with rewards programs, wholesale suppliers with regular dealers.
It makes less sense if purchases happen once every few years (furniture, electronics, real estate) or if your audience is small and irregular. People won't install a separate app for a single purchase. In those cases, it's better to invest in a fast mobile website, and for some tasks a progressive web app that doesn't need to be downloaded from an app store will do the job.
Options: for customers, for partners, for your team
A customer app competes for space on the phone, so it has to be fast and offer real value: rewards, quick reordering, early access to deals. The upside is a direct communication channel without paying for ads. The downside is that you'll need to promote it; it won't build an audience on its own.
An app for dealers and wholesale customers is simpler in design but more complex in logic: custom pricing, credit limits, documents. On the other hand, it's guaranteed to get used, because it saves time on calls and emails.
An employee app isn't published publicly at all. It replaces paper forms, messaging apps, and spreadsheets. Here, reliability and offline mode matter more than flashy animations.
Native development or one codebase for both platforms
For most store or loyalty apps, cross-platform development with Flutter or React Native is enough: one codebase for iOS and Android, lower cost, and easier maintenance. Native development in Swift and Kotlin is needed when the app relies heavily on the camera, background location, external devices such as scanners and payment terminals, or complex animation. We recommend an approach once we understand your goals, not out of habit.
Integrations an app needs to sell
Customers see the same things in the app as on your website: up-to-date prices, stock levels, order status. That's why most of the work usually goes into data sync, not the interface. We most often connect:
- a CRM or accounting system (Salesforce, HubSpot, QuickBooks) for orders and customers;
- card payments, Apple Pay, and Google Pay via Stripe or PayPal;
- UPS, FedEx, USPS, and other carriers with shipping rates and tracking;
- a push notification service such as Firebase or OneSignal;
- your rewards system, if it already runs at your point of sale or on your website.
Learn more about connecting systems in our section on integrations and automation.
What to prepare before kickoff
- A description of who will use the app, in what situations, and which action they'll take most often.
- Access or documentation for the systems the app needs to sync with: website, CRM, accounting, payments.
- Brand guidelines, logo, and copy, if you have them.
- Apple and Google developer accounts registered to your company, so the app belongs to you, not the contractor.
How to tell if the app is working
Download numbers alone don't say much. We recommend tracking how many people return to the app, what share of orders comes through it, how often customers buy again, and how many people turn off notifications. We set up analytics before release so you see the real picture from day one.
For dealer and employee apps, the yardstick is different: how many orders moved from phone calls and messaging apps into the app, how much time managers save on routine tasks, and whether order errors have dropped. We discuss these metrics with you at the start, so there's a baseline to compare against later.
Common mistakes
- Copying the website into the app. Users won't see the difference and won't have a reason to install it.
- Cramming everything into the first version. A big launch takes longer to test and breaks more often. It's better to ship the core and add features based on feedback.
- Sending too many notifications. Users turn them off or delete the app.
- Forgetting about maintenance. New versions of iOS and Android come out every year, and the app needs to be updated.
What affects cost and timeline
- Number of user flows: just catalog and ordering, or also loyalty, booking, chat, and a dealer portal.
- Platforms and approach: one codebase for both platforms or separate native apps.
- Integrations: whether your systems already have an API for data exchange or one needs to be built.
- Backend: whether your existing website can be used or a separate one is needed.
- Design: standard platform components or a custom visual language with animations.
We calculate the cost once the scope of the first version is clear, itemizing screens, integrations, and backend work separately.
FAQ
We already have an ecommerce store. Do we need a separate catalog for the app? No. The app usually pulls products, prices, and orders from the same store or accounting system.
Who publishes the app on the Apple and Google stores? We prepare everything for submission and handle the review process. The app is listed under your developer account.
Can we start with one platform? Yes, but with a cross-platform approach the second platform costs relatively little, so we usually launch on both at once.
What happens to the app after launch? It needs updates for new OS versions, bug fixes, and improvements based on feedback. You can hand this off to us as part of our app support and development services.
Why Promodex
We have 750+ projects under our belt and have been in business since 2015. Our team of 30+ includes designers, developers, and marketers. Our mobile portfolio includes Too Good To Go, which we contributed to. We'll tell you honestly if a website is enough for your business for now, and when you do need an app, we'll help you not only launch it but also bring in users and keep improving it after release.