01
“Customers keep asking if we have an app.”
If the website already does everything an app would, we say so and scope a mobile website instead. An app earns its place with repeat use, push, camera, location or offline access.
One app, iOS and Android.
Still shipping updates next year. One app for iPhone and Android, built with Expo and React Native on your existing Laravel, WordPress or WooCommerce backend. Store accounts in your company's name, plus help with review and yearly upgrades.
Customers use you a few times a year? A fast mobile-friendly website serves them better.
Honest before clever
Next in Build
Process Automation & Integrations
Invoices, quotes and data moving between your tools on their own.
What it is
An app on the data you already run, kept shipping
Reactll builds mobile apps for iOS and Android from one shared Expo and React Native codebase. They are for businesses that already run a website, platform or store and want an app on the same data.
You get the app and the API it needs on your existing Laravel, WordPress or WooCommerce backend. You also get store accounts in your company's name, and help with review and yearly upgrades. We run our own apps, Estimonia and Real Estate Club Dubai, and built the iOS app for The Status Network's members.
Mobile Apps covers the app and the API it needs on your backend. If the business system does not exist yet, start at Custom Platforms & Portals or Marketplaces. An app left behind by a previous developer starts with Project Rescue or Takeover & Handover. A PWA (a website that installs like an app) is cheaper and skips store review. But on iPhone, its push notifications only work after users add the site to their home screen.
What walks in
Most app work starts with one of three sentences
01 / 03
01
02
“Our app hasn't been touched in two years and won't build.”
An app left by a previous developer starts with a takeover or a rescue. Then the yearly upgrades Apple and Google require run on a schedule, before the stores enforce them.
03
“Apple rejected us and the email doesn't explain why.”
We read the rejection and fix the cause: a website in an app wrapper, no way to delete an account, privacy details that do not match, or no login for the reviewer. Then we reply to the reviewer.
What we already know
The details that decide whether it holds up
-
01
Plan for itApple rejects apps that are only a website in a wrapper
An app needs to do something the site cannot. If users can create an account in it, they must be able to delete it there too. The Status Network had account deletion from the start.
-
02
Reviewers need a way in
Apps behind a login get rejected when the reviewer cannot sign in. So we provide a demo account, or let the first screens work without one, as Estimonia and Real Estate Club Dubai do.
-
03
Register developer accounts as an organisation, early
Apple asks for a D-U-N-S number (a company ID number), which takes time. New personal Google Play accounts must run a closed test with at least 12 testers for 14 days. Company accounts skip this.
-
04
Over-the-air updates (fixes sent straight to phones) have limits
Changes to JavaScript, styling and images can skip review. Native code, new permissions or a new Expo version need a new build and review. We use these updates for fixes, not to change what the app does behind the reviewers' backs.
Who it is for
An app earns its place when people come back
A PWA (a website that installs like an app) is cheaper and skips review. But on iPhone, its push notifications only work after users add the site to the home screen.
Good fit
Same Data, New Front End
You run a Laravel platform, WordPress community, WooCommerce store or API, and want an app on the same data.
Good fit
A Task People Repeat
People repeat a task often enough to keep an app on their phone, or need push, camera, location or offline reading a website does poorly.
Good fit
An App That Stopped Shipping
An existing app has stopped building, keeps getting rejected, or nobody can ship an update any more.
Not a fit yet
A Few Visits a Year
A fast mobile-friendly website serves them better. Deep phone-specific work such as custom AR needs a native specialist team. An app shipped once and left alone still needs a budget for running it.
How it runs
From the first question to the yearly upgrade
-
Step 01
App, Web or Both
If a mobile website would do, we say so and scope that. Apple rejects apps that are only a website in a wrapper, so the app must do something the site cannot.
-
Step 02
API and Store Accounts
We open company accounts in your name early. Apple asks for a D-U-N-S number, which takes time, so the checks run alongside design.
-
Step 03
Testers on Real Devices
From the first weeks, your team uses test builds (TestFlight and Google Play testing) on their own phones. Crash reporting is set up before the first beta.
-
Step 04
Submit and Keep Current
We prepare listings, privacy details and a demo account for the reviewer. Then come over-the-air fixes and yearly upgrades. Native code, new permissions or a new Expo version still go through review.
In production
We run our own apps. That is where the advice comes from
FAQ
Questions people ask before an app
It is a fixed price agreed before any code is written. When the backend already exists, it is a standard Build. A new backend, offline use and unusual phone features raise the price. Keeping it running after launch is a monthly Run plan. Current prices are on our pricing page.
If people use you a few times a year, a PWA (a website that installs like an app) or a good mobile website is usually better. An app is worth it when people come back often, or need reliable push, camera, location or offline access.
Yes, that is the usual case. We add an API to Laravel or build it as a WordPress plugin, as with Real Estate Club Dubai and The Status Network.
Yes. We read the rejection and fix the cause. It may be a website in an app wrapper, no way to delete an account, privacy details that do not match, or no login for the reviewer. Then we reply to the reviewer.
