01
Scenarios and roles
We discuss who will use the app, which actions matter, and which screens belong in the first version.
SRV-14
iOS and Android app in 14 days
We build a working mobile app for a service, business, community, or internal process.
Base app launch.
250,000 RUB
After the vision is approved and development is paid.
14 days
14 days
How the work starts
First we understand what the app should do. Then we show the vision, approve it, and move into development.
02
Up to three directions
We show up to three visual options to settle style and logic before development.
03
Build and launch preparation
After approval and payment, we build the app, check the key scenarios, and prepare publication.
Fourteen days after the start
The timeline starts once the direction is approved and paid for. The app comes together stage by stage, and every stage is visible.
- Day 0 — Start
- Days 1–3 — Screens and scenarios
- Days 4–9 — Interface build
- Days 10–12 — Logic and states
- Day 13 — Device testing
- Day 14 — Publication preparation
- Day 0
Start
We lock in the approved direction, scenarios, and the order of work.
- Days 1–3
Screens and scenarios
We assemble the screen structure and the main user path.
- Days 4–9
Interface build
We turn the approved design into a working app for iOS and Android.
- Days 10–12
Logic and states
We connect screens, data, and key scenarios, and check errors and empty states.
- Day 13
Device testing
We walk through the app on real phones and fix what we find.
- Day 14
Publication preparation
We build the final version, prepare store materials, and hand over the build.
We need context, not a technical spec
Explain the idea, audience, and desired result. We turn it into initial screens, scenarios, and a build plan.
- What the app does and who it is for.
- Which main actions should happen inside.
- Whether accounts, payments, notifications, or content are needed.
- Which apps feel close to the target and which ones do not.
What the base launch includes
The base price fits a first working version with a clear scenario and shared logic for iOS and Android.
What the base launch includes
- Screen structure and user scenario.
- Up to three design directions before development.
- Interface for iOS and Android.
- First working build.
- Publication preparation and access handoff.
- Materials for App Store and Google Play pages.
Complex functions are scoped separately
If the app needs accounts, data, or integrations, we estimate that before the start.
- Authorization, registration, and user profiles.
- Admin panel for content, requests, or orders.
- Storing and processing personal data in a database under Russian 152-FZ requirements.
- Telegram Mini Apps as a separate or connected scenario.
- Server, database, payments, notifications, and integrations.
An app should be findable too
Stores and search follow their own rules. We prepare the app and its pages so people can find them.
Store promotion and ads are separate work. Basic findability is part of the launch.
Store pages
We prepare the name, description, and materials for the App Store and Google Play together with you.
App website
If the app needs a public page, we build it with search titles and descriptions.
Speed and size
The app is built to open fast and not annoy people.
Yandex and Google
We connect the public pages to Yandex Webmaster and Google Search Console.
We tell you what the law requires
Apps almost always handle people's data. We tell you in advance which documents and consents are needed, including under the Russian personal-data law 152-FZ.
- 152-FZ
Personal data
If the app collects user data, it needs a policy and consents. We tell you which ones and where.
- STORE
Store requirements
The App Store and Google Play require a privacy policy and an honest data description. We prepare the pages and texts.
- CONSENTS
In-app consents
We show where consents belong in the app so forms and notifications work by the rules.
- OFFER
Payments and offer
If the app takes payments, it needs a public offer and company details. We explain what to add and where.
We are not a law firm and do not replace a lawyer. But we know what the law and the stores usually require and will guide you through it.
An app also needs infrastructure
Developer accounts, server, database, and app stores are not always part of the base scope.
01
Accounts should belong to you
App Store and Google Play publication usually require your developer accounts and owner data.
02
You can buy the server
If the app needs data, users, or sync, the server and database can be registered to you.
03
Review time is not fully ours
We prepare the app for publication, but App Store and Google Play review timing depends on the platforms.
Projects you can inspect
Before starting, you can inspect how JOURLOY works with public products, visual language, and launch.
Common questions
When do the fourteen days start?
The timeline starts after the design direction, scope, and development payment are approved.
Can user accounts and a server be included immediately?
Yes, but that adds cost and time. We estimate that scope separately before the start.
Is app store publication included in the timeline?
We prepare the app for publication, but final App Store and Google Play review depends on the platforms.
Are findability and SEO included in the price?
Yes, the foundation is included: store pages, a public app page with metadata, and connection to Yandex and Google. Ads and promotion are separate.
Do you help with the data policy and consents?
We tell you what 152-FZ, the App Store, and Google Play require and prepare the needed pages and texts. Your lawyer can review them if you want.
What stays with me after launch?
The app is yours: the accounts, the build, and the materials are handed over to you. Further development is discussed separately.
SRV-14
Tell us what app needs to be built
Describe the idea, audience, and main scenario. We will reply with questions, scope, and a starting option.
JRL-FORM
Request
Share the idea and I will get back to you
Briefly describe the task and leave one preferred reply channel: email, Telegram, WhatsApp, or Max.
REC
- Service
- 14APP
- Channel
- Contact
- —
- Idea
- 0 characters
- Consent
- 0/2
Ready0/4
You can also write directly:
hello@jourloy.com