Skip to content
Oxarus
STUDIO · MOBILE

in
pockets,
every
day.

End-to-end app development for iPhone and Android. They keep working when the connection drops and send notifications at the right moment, and we run the whole process from store review to launch.

  • iOS and Android at the same time
  • Works offline
  • App Store and Google Play submissions included
Illustrative app screens.
Two devicesOfflineNotification
DEVICE

everything
the
phone
can
do.

Apps do what websites can't. Pick one and see how it works on a phone.

VisionKit · Illustrative screen

STORES

launch
is
part
of
the
job.

Test builds, store reviews, rejected submissions. We track all of it; you just see that the new version is live.

App Store

iPhone and iPad

v2.4.0Waiting
  1. 1Build14 min
  2. 2TestFlight35 min
  3. 3Apple review~24 h
  4. 4Livenext day

Google Play

Phone and tablet

v2.4.0Waiting
  1. 1Build12 min
  2. 2Closed testing1 h
  3. 3Google review~6 h
  4. 4Livesame day
Staged rollout
0%

release.logRepresentative

2.4.1 · same day

Small fixes reach users the same day through in-app updates, without waiting on the stores.

AFTER LAUNCH

keeping
it
running
is
on
us.

After every release we check the same dashboard: is the app crashing, are users updating, what are the ratings saying?

Brewline · live · v2.4.0

99.8%

Crash-free sessions

  • iOS99.83%
  • Android99.71%

99.52%99.84%

Store rating

4.8

2,184 ratings

  • 586%
  • 48%
  • 33%
  • 21%
  • 12%

Version adoption

First 14 days after release

0%
9%
24%
38%
50%
59%
65%
70%
73%
75%
76%
77%
78%
78%
  • 2.478%
  • 2.318%
  • Other4%

Startup time

0.9 s

iOSp50 0.8 s · p90 1.3 s

Androidp50 1 s · p90 1.7 s

Daily sessions
18.4K
ANR rate
0.21%
API errors
0.08%

Recent events

  • 2.4.0 live on the App Store09:40
  • Android rollout reached 100%08:12
  • Slow startup on older devices, fixed in 2.4.1yesterday
  • Crash rate stayed below thresholdyesterday

Illustrative values; the real dashboard is set up per project.

TECHNOLOGY

one
codebase
or
two
apps?

There's no single right answer. We choose per project and tell you why up front.

When it fits

  • When the app and web will evolve together
  • When the first release needs to ship fast
  • When most screens are lists, forms and content
Shared code
85–95%
First release
8–12 weeks
Device access
Via modules
Workflow
One workflow

The right starting point for most business apps.

Scanner.tsxapp.json

Build outputsTwo apps from one source

  • iOSScanner.tsxBrewline.ipa
  • AndroidScanner.tsxbrewline.aab

MOBILE

let's
put
your
app
in
their
pockets.

Tell us what you want your users to do on their phones. Together we'll pin down which approach fits and what the first release covers.

info@oxarus.com