Skip to main content
GullySystem

Mobile Application Development

Mobile application development covers choosing the approach, building the app, testing it on modest handsets and publishing it to the stores. It also covers the maintenance that the stores expect once an app is live.

Share your requirements

Choosing what to build with

Cross-platform

React Native or Flutter suits most business apps, with one codebase and one release cycle. Most projects begin on this route.

Native

Kotlin or Swift is used where hardware, performance or platform features drive the app. The cost is two codebases, two test cycles and two store reviews for each release.

A wrapped web app

Sometimes it is a cheap and honest choice, and sometimes it disappoints. It depends on what the app has to do.

Testing on phones people own

Low-end Android

The app is checked on modest handsets. Memory is limited, and the Android version is old.

Poor connections

Screens are tried on a throttled line, and not only on office wifi.

Upgrade paths

A user with old data on the phone keeps it through the next release. Data survives updates.

Publishing and what follows

Store accounts in your name

The app belongs to your company, and the developer who built it does not hold the accounts.

Reviews and rejections

Privacy declarations, permissions and screenshots are prepared in advance, because both stores ask what the app collects and why, and a vague answer delays the release.

Crash reports

Failures on real devices come back with enough detail to be fixed.

FAQ

Frequently asked questions

How does a mobile app project usually start?

With the two or three tasks people will do on a phone, written down plainly. Screens follow from those tasks, and whatever belongs on a desktop stays there.

Is the app maintained after launch?

Yes, under a support arrangement, and most apps need one. Operating systems change every year, and an app left untouched can eventually be refused by the stores. Updates keep it listed.

Can one app serve staff and customers together?

Usually it should not. The two groups need different screens and different rights, and mixing them makes the app harder to use and harder to secure.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

What happens after you share your requirements

  1. A senior engineer reads your answers. Nobody phones first.
  2. Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
  3. If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
  4. No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.

Share your requirements