Challenges
- How can a complex VPN service be adapted for the Telegram mini-app so that users don't get lost in the details and quickly get to the main goal?
- How can you make onboarding clear if your product is technical and requires trust from the user?
- How can I integrate payment and, if necessary, TON wallet integration without breaking the flow or looking too complicated?
- How should we design error, loading, and confirmation states so that the service remains understandable even in non-standard scenarios?
Product and subject area analysis
During the initial phase, the following were examined:
- product documentation;
- service architecture;
- user roles and scenarios;
- Telegram guidelines and limitations;
- data storage and inheritance principles;
- product business goals.
The goal was to map out user scenarios and understand the product's technical limitations.
Conducted interviews with potential users
The goal of the interview is to identify the criteria for selecting a VPN, barriers to connection, and factors influencing the decision to purchase and continue using the service:
- how users choose a VPN;
- what factors influence the decision to connect;
- why users stop using a VPN;
- what influences the decision to pay for the service;
- what expectations and concerns arise before connecting.
