Vitto Android launch

Android Engineer20211+ year3 people2 min read

Built the first Android foundation at Vitto, including multilingual voice onboarding, open testing with 300 users, and the app story behind a 200K USD pre-seed raise.

Overview

At Vitto, I joined early enough to shape both the Android product and the team’s delivery habits. The role mixed hands-on product building, release feedback, and foundations for future Android hiring.

Problem

The company needed to move from an early product idea to a usable Android app while learning from real users quickly.

Constraints

  • The product direction was still evolving, so Android choices needed to stay adaptable.
  • The app had to feel real enough for users and investors while still moving quickly.
  • Feedback loops needed to be established before broader launch confidence existed.

Approach

I built the consumer Android foundation, implemented multilingual voice onboarding with Android Text-to-Speech, ran Google Play open testing with 300 users, and helped the team scale Android scope responsibly.

Key decisions

Build onboarding with multilingual voice support

Reasoning

Voice support made onboarding more approachable and gave the early product a clearer identity.

Alternatives considered
  • Keep onboarding text only

Use open testing as an active product-learning loop

Reasoning

The team needed real feedback before scaling distribution. Play open testing created a practical loop for product learning.

Alternatives considered
  • Limit validation to internal QA and small manual demos

Tech stack

  • Kotlin
  • Android Text-to-Speech
  • Google Play Open Testing
  • CI/CD
  • Android

Result and impact

  • First Android hire
    Android role
  • 300 users
    Open testing cohort
  • Supported 200K USD pre-seed funding story
    Business milestone

The Android app moved from early concept to a real product foundation, giving the team user feedback, release confidence, and a platform to build on.

Learnings

  • Being an early mobile hire means owning both product interpretation and engineering direction.
  • Release channels are valuable not just for QA, but for learning what users actually need.
  • Foundational Android decisions matter more when they become the template for future hires.

Early-stage Android work forces clear trade-offs. You need to ship enough to learn, but the foundations still have to be strong enough for the next stage of growth.

All projects