Our client is a mobile VPN service. We built its app end to end, from analysis and design to development and launch. In this case study we explain what a product like this is made of and how we approach each stage of building it.
A VPN app looks simple: one big "Connect" button. But behind that button are system permissions, server infrastructure, subscriptions and some of the strictest app store review there is. This breakdown will be useful to anyone planning end-to-end mobile app development, especially for a service or subscription product.
The brief: a VPN service as a mobile product
Our task was to build the VPN service's mobile app in full, with no ready-made design and no inherited code. A project like this brings together three different worlds: an interface for ordinary people, low-level networking on the device, and the server side that carries the traffic.
VPN users usually don't know much about protocols or encryption. They want the connection to be secure, the internet not to slow down, and the app to stay out of the way. So we position a product like this as a tool for protecting your connection and privacy, for example on public Wi-Fi, and build the whole interface around that job.
Hence the core principle: all the complexity stays inside, outside there is one clear action. Anything that asks the user to make technical decisions is either removed or tucked away in settings.
All the complexity of a VPN stays inside the app; on the outside there is one clear action.
Home screen: one-tap connection
In a VPN app, people spend almost all their time on the home screen. They open the app to turn protection on or off and close it right away. That's why mobile UX for this kind of app is designed starting from the home screen, not from the menu.
The home screen of a typical VPN service has to answer four user questions:
- Am I protected right now? Connection status should be readable in a second: color, label, button state.
- How do I turn it on or off? One large button, easy to reach with a thumb.
- Which location am I connected through? The current server and a quick way to pick another.
- Is everything working properly? Session time, speed or another clear sign that the connection is alive.
We also design the in-between states: "connecting," "reconnecting," "no network," "server unavailable." These are the moments when users get nervous and delete the app. Each state needs its own look and clear copy, not an endless spinner.
Choosing a location and showing speed
The server list is the second most important screen. It usually has a default "fastest server" option, a list of countries or cities, search and favorites. If there are many servers, it helps to show load or latency next to each one so people don't pick at random.
Showing speed is a delicate point. The numbers have to be honest and understandable, or they raise more questions than they answer. So during design we decide what exactly to measure and how to present it together with the team responsible for the server side.
Onboarding and system permissions
For a VPN to work, the operating system has to let the app manage the network connection. On iOS the user sees a system prompt to add a VPN configuration; on Android, a dialog asking for permission to connect. The wording of these windows is set by the system, and to an unprepared person it sounds alarming.
So we build the app's onboarding around this moment. Before the system window appears, the user should understand what is about to happen, why it's needed and what the app does with their data. Good onboarding is short: two or three screens, without a tour of every feature.
There are also platform differences that affect design and development:
| iOS | Android | |
|---|---|---|
| System mechanism | Network Extension | VpnService |
| First connection | Prompt to add a VPN configuration | Dialog asking permission to connect |
| Background operation | Managed by the system via the extension | Persistent notification that the VPN is on |
| Subscriptions | App Store in-app purchases | Google Play Billing |
Subscription and free trial
Most VPN services make money on subscriptions, so the paywall is as much a part of the product as the connect button. An in-app subscription is designed together with the main flow: when to show the offer, what is available for free, how the trial works and what people see when it ends.
When designing the subscription, we work through several questions:
- which plans are needed: by term, by number of devices, by set of locations;
- whether there will be a free trial and how users will know when billing starts;
- how to restore a purchase on a new phone and how to cancel the subscription;
- how the app checks subscription status on the server so that only paying users get access.
For in-app digital subscriptions, the stores usually require their own billing systems, and the terms depend on the platform and country. So we agree on the payment setup with the client before designing the screens: it shapes the copy, the flows and the server logic.
Another principle: canceling a subscription should be as clear as buying one. The stores check that terms are transparent, and users who feel tricked leave bad reviews and request refunds.
Publishing on the App Store and Google Play
VPN is one of the categories the stores treat most strictly, since the app gets access to all of the user's traffic. Publishing such a product on the App Store and Google Play takes preparation that should start in parallel with development.
Well-known requirements we build in from the start of the project:
- On the App Store, VPN apps are published from an organization developer account, not an individual one.
- On Google Play, use of VpnService has to be declared, and it is allowed when VPN is the app's core function.
- The privacy policy must state plainly what data is collected and how it is used.
- The data disclosure forms on the store listing must match what the app actually does.
- Subscription, trial and auto-renewal terms are visible to the user before payment.
We also take the legal side into account. Different countries have their own rules for VPN services. How and where to distribute the product is decided by the client with their lawyers, and we build in what that requires: accurate copy, transparent data handling and the ability to manage available regions flexibly.
Server side and infrastructure
A VPN service's mobile app is only the visible part. Behind it are the servers that carry the traffic and a backend that manages users, subscriptions and the list of locations.
Broadly, the server side of such a product handles several tasks: tracking users and devices, checking subscriptions, issuing connection configurations, maintaining the server list with its status, and monitoring availability. It matters that locations and settings can be changed without shipping a new app version: store review of an update takes time, and a server may need replacing today.
A privacy service has one more requirement: collect only the user data needed for the service and billing to work. That decision is made at the architecture level, not in the wording of the privacy policy.
How we ran the project: stages of work
We ran the project through our standard stages. For a VPN app, each of them has its own specifics:
- Analysis, structure and messaging. We study the market and competitors, user scenarios, the monetization model and store requirements. The output is a map of screens and states, including errors and in-between statuses.
- Visual identity and design. We propose options in different styles and design the interface from scratch, with special attention to the home screen, onboarding and the paywall.
- Development. The interface, the networking layer built on each platform's system mechanisms, subscriptions and the connection to the server side.
- Testing. We test connections on different devices and OS versions, on mobile data and Wi-Fi, when the network changes or drops, as well as purchasing, restoring and canceling a subscription.
- Publishing and launch. We prepare the store listings, privacy policy and data disclosures, go through review and respond to store feedback.
Other projects we have delivered the same way are collected on our work page.
Analytics and growth after launch
A subscription app only really starts working after it is published. From there the team watches where users drop off and improves the product based on data, not gut feeling.
For a VPN app it's useful to track several groups of metrics:
- Funnel: install, onboarding completion, VPN permission granted, first connection, subscription or trial started.
- Connection quality: share of successful connections, drops, connection time by location.
- Stability: app crashes by OS version and device model.
- Subscriptions: trial-to-paid conversion, renewals, cancellations.
We collect analytics in a VPN app carefully: the product promises privacy, so events describe actions in the interface, not where a person goes online. Product metrics must not contradict the product's promise.
On top of that, the app needs updates for new versions of iOS and Android, monitoring of store rule changes and ongoing server maintenance. This is continuous work that is best planned together with the first version.
FAQ
How long does end-to-end mobile app development take?
It depends on the scope of the first version, the number of platforms and the server side. For a VPN app, the timeline is driven most by infrastructure setup, subscriptions and app store review. A realistic timeline comes from an estimate after the analysis stage, once the set of screens and integrations is clear.
Can you build an app for iOS and Android at the same time?
Yes. The interface can be shared or cross-platform, but the VPN networking layer on each platform is written using its own system mechanisms: Network Extension on iOS and VpnService on Android. That's why the connection has to be tested separately on both systems and on different devices.
Why does a VPN app take longer to pass review?
The stores treat VPN as a sensitive category because the app gets access to the user's traffic. Reviewers check who is publishing it, how data collection is described, what the privacy policy says and how subscriptions work. The more carefully this is prepared, the fewer rejections you get.
What happens with the app after it is published?
You monitor connection stability and crashes, watch the funnel from install to subscription, ship updates for new versions of iOS and Android and keep the servers up to date. For a subscription product, post-launch development is routine work, not a separate project.




