Built it with AI? We take it to the App Store and Google Play.
VibeToStore is a fixed-fee service from Codixus. You built the app with an AI tool; we handle the store side: the listing, the privacy forms, the build upload, the submission and the replies to the review team. $299 for one app on both stores.
Building an app got fast. Getting it through App Review did not. First submissions often stall on the things an AI tool does not do for you: a privacy policy, the data safety form, account deletion and sign-in rules, screenshots in the right sizes, a build signed with the right account. We do this work for our own apps, and we will do it for yours.
There is no checkout on this page. You write to us, we look at the app and reply with whether it fits the fixed fee. Mention VibeToStore in your message so we know which service you mean.
What the fixed fee covers
One app, both stores, from the first check through the store review.
Store-readiness check
Before anything is submitted we run your app and read it against the App Store and Google Play rules. You get a short list of what would get it rejected: missing account deletion, a payment flow the stores do not allow, placeholder content, missing permission texts.
Listing on both stores
Name, subtitle, description, keywords, category and age rating, written from your material and sent to you for approval. Screenshots are taken from the running app in the sizes the stores require.
Privacy and data forms
The App Privacy answers on App Store Connect and the Data safety form on Google Play, filled in from what the app actually collects. If you have no privacy policy page yet, we tell you what it has to cover.
Signed builds, uploaded
Bundle identifiers, certificates, upload keys and the production builds are prepared on your own developer accounts. The app is published under your name and stays yours. On an individual Apple membership, Apple gives only the account holder access to certificates and identifiers, so the signing setup is done at your own login, with us guiding you.
Submission
We submit the app for review on both stores, with the review notes and the test account the reviewers ask for.
Review follow-up
We answer the review team and resubmit until the app is approved, or until a rejection needs a change inside the app. Then we tell you exactly what to change, and resubmit once it is changed.
How it works
You write to us
Tell us which tool you built the app with and where the code lives. We reply with whether it fits the fixed fee.
We check the app
You give us access to the project and add us as a user on your developer accounts. We send you the list of store blockers.
We prepare and submit
Listing, forms, signed builds and the submission on both stores. You approve the listing before it goes out.
We follow the review
We reply to the review team and resubmit until the app is approved or a rejection needs a change in the app. You hear about every message.
One fixed fee
The fee covers the readiness check, the listing, the privacy and data forms, the signed builds, the submission on both stores and the review follow-up until the app is approved or a rejection needs a change in the app. Making that change is not part of the fee; resubmitting after it is. The developer account fees that Apple and Google charge are paid to them and are not part of it.
RevenueCat setup, as a separate add-on
Subscriptions and in-app purchases need products on both stores, entitlements and a paywall wired to them. We set this up with RevenueCat as a separate add-on. Mention it when you write to us.
What you need
Your own developer accounts
An Apple Developer account and a Google Play Console account, in your name or your company's. You add us as a user; you never share a password. On an individual Apple membership the signing setup is done at your own login, with us guiding you.
Twelve testers, if your personal Google Play account is new
Google asks personal developer accounts opened after 13 November 2023 to run a closed test with at least 12 testers, opted in for at least 14 days in a row, before an app can go to production. The testers are yours to find. We set up the closed test and apply for production access when the 14 days are over. Google then reviews that application, usually within seven days. If the testers did not use the app enough, Google can ask for more testing before it grants access.
An Expo or React Native project
Several AI app builders export exactly this for mobile, and it is the stack we build our own apps on. An app that only runs on the web is a different job: ask us first.
An app that runs
We publish what you built. Redesigning it or adding features is not part of this fee.
We go through the same review ourselves
Codixus is a product studio. Our own apps are on the App Store and Google Play, and every release goes through the same forms, the same signing and upload steps and the same review.
See our apps →