Mobile app development and store publishing

What we do

Technologies we use

Both options below share one codebase across iOS and Android. Compared with building each platform separately, that ships faster and costs less to maintain.

From code to a live listing

1. 01

   Agree scope and design

   Feature list for the first release, screen flow, interface. Code starts once that is settled.

2. 02

   Build and test on real devices

   Delivered in batches so you can use it early. Permissions, push notifications and location behave differently on a simulator, so we test on real hardware.

3. 03

   Set up the publishing accounts

   The Apple Developer and Google Play Console accounts are in your name. We walk you through registration and verification, then take access to submit builds.

4. 04

   Signing and release builds

   Certificates and provisioning profiles on Apple, keystore on Google. The signing keys go to you. Lose them and you lose the ability to update the app.

5. 05

   Prepare the store listing

   Icon, screenshots at the right size for each device class, title and description, keywords. Then age rating, data disclosures and a privacy policy link.

6. 06

   Submit for review

   Send the build and track it. If it comes back, read the reason, fix that specific thing and resubmit.

7. 07

   Release and watch

   Pick the release date. For the first few days we follow crash reports and reviews, because some bugs only show up on real users' phones.

Projects we have built

Frequently asked questions

How long does publishing to the stores take?

Apple usually comes back within one or two business days. Google Play is quick too once an account has been running a while. First submissions often trigger follow-up questions, so budget one to two weeks for the whole release step.

How much do developer accounts cost?

Apple charges yearly, Google charges once at registration. At the time this page was updated that was 99 USD a year and 25 USD once. You pay Apple and Google directly; Solv does not collect it. Both can change their pricing, so check their official pages before you register.

Whose name are the developer accounts in?

Yours, or your company's. Solv does not publish apps under its own account. That would leave your app and your users' data in someone else's hands. Changing development partners later also becomes hard. We take only the access needed to submit builds, and you can revoke it whenever you want.

What if the app gets rejected?

A rejection on the first submission is normal. Apple and Google both name the guideline you fell foul of. We read the reason, fix that specific thing and resubmit. The usual culprits are a missing demo account for the review team, vague permission descriptions, or no privacy policy link.

What needs preparing before submission?

Icon, screenshots at the right size for each device class, title and description, keywords. Then age rating, data disclosures, and a privacy policy link anyone can open. If the app has a login, include a working test account for the review team. Skip that and it almost certainly comes back.

Will React Native or Flutter get the app rejected?

No. Apple and Google judge what the app does and how finished it is, not what you built it with. Plenty of familiar apps on both stores are cross-platform. I'm Alive was built by Solv with React Native and cleared review.

Is there anything to do once the app is live?

Yes. Apple and Google periodically raise the minimum SDK version and tighten permission and privacy rules. An app that falls behind can have updates blocked, or get pulled. There are also bugs that only surface across the full range of real devices. Solv covers that with ongoing maintenance.