Choice of approach
Cross platform development is cheaper and faster, native gives the most capability and smoothness.
The first decision of the project is native or cross platform development. Budget, deadlines and capabilities depend on it.
Cross platform development is cheaper and faster, native gives the most capability and smoothness.
Scenarios, prototypes, design following the rules of each platform, and they differ.
The application and the server side, if one is needed.
Local storage and synchronisation once the network appears. Critical for field staff.
Setting up delivery and segmentation, without turning into spam.
Setup in the application stores, preparation of descriptions and screenshots, passing moderation.
The first version starts at three months. Store moderation is added to the development time and takes several days upwards.
Who will use it and why, how often. That determines whether the application is needed at all.
Scenarios and layouts following the rules of each platform.
In iterations, with interim builds for testing on real devices.
Developer accounts, upload, moderation, release of updates.
Developer accounts in the stores must be registered to your company. If the application is published from the contractor account, parting with them costs you both the application and every user who installed it. This is arranged at the start of the project, not at the end.
Cross platform is around one and a half times cheaper and suits most business applications: catalogues, personal accounts, requests. Native is needed for complex graphics, intensive camera work and wherever maximum smoothness matters.
Often it is, and that is the first thing we check. An application pays off with regular use and a need for notifications, offline work or device functions. For one off visits a user will not install anything.
An application cannot be released and forgotten: the platforms release new system versions, and without updates an application stops working correctly within a year or two, after which it is removed from publication. Plan regular updates as a mandatory line item.
Tell us who will use it and how often. We will say honestly whether an application is needed or a responsive site is enough.
Request received
We can already see it. We will reply within one business day, and for urgent matters we will bring in the on-duty engineer right away.
City not found. Please check the spelling.