About The Team

This is a results-oriented mobile app team.

Team size ~50, covering product, tech, design, growth, and ops. We don't build org efficiency on handoffs. We keep project teams continuous from judgment to launch to results.

~50 People Product, tech, design, growth, ops working together
Multi-project Parallel Not organized around a single product
Project Teams Own End-to-End Judgment, launch, data review stay continuous
Shared Methods Effective experience becomes the next starting point
Project Studio

Project teams advance independently. Responsibility stays intact.

Project teams keep pushing their direction. From judging opportunity, building v1, handling store pages to reviewing acquisition and retention—we avoid breaking the flow into disconnected steps.

  • Shorter decision chains
  • Faster feedback into next version
  • Clear ownership and accountability
Shared Methods

Shared capabilities codified. Less repeated trial and error.

Not every project starts from zero. Effective store packaging, asset testing, acquisition rhythm, and retrospective methods flow back into the team and become reusable for the next project.

  • Store page and asset methods reusable
  • Unified data metrics
  • Lower collaboration cost
Cross-function

Different roles, different work. Same goal.

We care more about roles collaborating around the same outcome than splitting each step into isolated KPIs.

P

Product

Judges opportunity, breaks down requirements, drives version cadence. Keeps the project clear on what comes first.

T

Tech

Keeps versions shipping. Keeps iteration from being slowed by technical debt.

D

Design

Owns UI, UX, and packaging quality. Also contributes to store presentation and conversion decisions.

MKT

Growth

Looks at store conversion, asset testing, and channel performance to see if each version can scale.

OPS

Ops

Owns daily rhythm, feedback collection, and data organization. Product judgment doesn't stop at"launched."

Culture

Pace can be fast. Judgment must be clear.

We want high execution efficiency—not driven by emotion or layers of approval. What matters more is clarity on goals, constraints, priorities, and data. Then move forward.

  • Clarify the problem before deciding the solution
  • Use data, not assumptions, to discuss priorities
  • Build collaboration on real results
Long-term View

Vision is not a slogan. It's the direction we work toward.

Vision: Become a team that continuously produces mobile digital products—not dependent on a single hit.

Mission: Build, launch, and iterate products worth making. Keep improving UX and outcome quality.

Values: Agile and pragmatic. Data-driven. Cross-role collaboration. Accountable for results.