From repo
to review
Every application moves through the same three stages in the same order. The gates between them are the reason a rejection is news here, not routine.
Plan
Nothing larger than a bugfix is written without a plan, and the plan is a file in the repository before it is code.
Gate
Lint at zero warnings, unit and snapshot tests, a written QA verdict. Red sends the feature back to code.
Ship
fastlane builds and uploads to TestFlight or the internal track. Then review, and whatever review asks for.
How a release passes
What we need from you
Two weeks before a release, not on the day.
| What | Who provides it | When | Cost or note |
|---|---|---|---|
| You | Two weeks before release | 99 USD a year | |
| You | Two weeks before release | .p8, downloads once | |
| You | Two weeks before release | 25 USD once | |
| You | Two weeks before release | Setup, API access | |
| We generate, you keep | First release | Stays on your side | |
| Together | At kickoff | Checked for conflicts | |
| We write, you approve | Before review | One for each app | |
| You confirm the facts | Before review | Play requires it |
Eight cells. An application ships when every one of them is filled.
Send us what is missing
The company
- Legal name
- EVERCODE, LLC
- Registered
- Tbilisi, Georgia
- Registration number
- 405881354
- D-U-N-S
- 933916034
- Founded
- 2026
- Based in
- Tbilisi, Georgia
EVERCODE, LLC builds mobile applications for companies that want to own what gets published under their name.
iOS in Swift and SwiftUI for iOS 17 and later. Android in Kotlin and Compose for Android 8 and later. One repository and one set of secrets per application, a release pipeline that is the same on every project, and store metadata written from scratch for each app.
We work inside your App Store Connect and Play Console as an invited team, on access you grant and can withdraw. The accounts, the keys and the published apps stay yours, including the day you stop working with us.
Questions we get
Whose store account do the apps live in?
Yours. We are invited into your App Store Connect and Play Console with the rights the work needs, and the application is published under your company name. We do not hold a portfolio of other people's apps under ours.
Who holds the signing keys?
You do. The App Store Connect API key, the certificate repository and the Android upload keystore live in your accounts and your secret storage. We work with access you can revoke in a minute, and a revoked key costs us a conversation, not your release.
What happens when review rejects a build?
We answer the reviewer and ship the fix. The originality passport exists so that the most common rejection, an app judged too close to something else, does not reach review in the first place.
Do we need twelve testers for fourteen days?
Only personal Google Play accounts created after 13 November 2023 have to run that closed test. An organization account does not, which is one of the reasons we ask you to register as one.
Who fills in Data safety and the privacy policy?
We draft both from what the application actually does, and you confirm the facts before anything is submitted. Each app gets its own privacy policy page on a URL that stays reachable for as long as the app is listed.
What do you need to start?
A conversation about the application, and the accounts listed above when the release gets close. Design, if you have it. If you do not, we work from the brief and show screens before the code is written.