We turned a cultural-learning idea into a branded, native product: short lessons, practical quizzes and offline access, with optional accounts and cloud synchronization.
Explore the work01The opportunity
A greeting, a meal or a first day at work can carry unfamiliar expectations. Broad facts about a country rarely tell someone how to approach the moment in front of them.
We organized learning around everyday interactions: communication, work, meals, relationships and other practical situations. The hypothesis is that a short, contextual lesson can be easier to use than a long country guide.
How could we make cultural context approachable, useful in the moment and available without a connection?
Start with a place and a practical category.
Learn one focused interaction through cards.
Use a quiz with feedback and completion.
Save lessons and progress locally; sync with an optional account.
02From zero to one
We shaped the idea, created its identity, designed the experience and built the system that makes it work.
Cultural context for everyday life. The product choices, visual language and architecture developed together. Our research combined product, domain and technical exploration to shape the decisions below.
We defined a pocket cultural companion around practical moments, short learning loops and value before sign-up.
We developed a reusable interaction taxonomy and reviewed content structure, consistency and rights. This was desk and editorial research, not a validated user study.
We created the chameleon identity, cream and navy foundation, emerald accents, category colors and rounded, friendly typography.
We designed culture selection, lesson cards, quizzes, saved content and progress, including empty, offline and account restoration states.
We built shared iOS and Android screens with Expo, native tablet support, bundled content and SQLite persistence.
We implemented optional Supabase accounts, conflict-safe synchronization, server-verified store purchases and the companion website.
A complete brand identity
We designed an identity for curiosity and respectful adaptation. The visual system is warm and inviting, with enough restraint for cultural guidance to stay central.
We created a connected identity system: logo, character, color, typography, iconography and interface patterns, then carried it into the website and distribution materials.
03Product judgment
What we chose, why it mattered and what it cost.
A stable category framework makes different cultures navigable through familiar needs. Situation metadata adds context while culture-specific extras require a distinct learning purpose. We avoided turning the experience into an endless list of facts.
A reusable taxonomy creates consistency but cannot represent every cultural nuance. Guidance needs clear editorial boundaries and continued review.
Lesson previews lead into short cards, a quiz with feedback and a completion state. Saved lessons and progress give the next visit a clear starting point. The short lesson format is a design choice, not a measured learning improvement.
Brevity limits depth. It supports an approachable starting point and makes each lesson easier to revisit.
Bundled content, quizzes, saved lessons and progress use local SQLite. Optional accounts add backup and cross-device benefits. Cloud errors preserve local learning, while revision-aware preferences and deduplicated progress events protect restoration.
Local and remote state require careful conflict handling. The benefit is useful guest learning and a more resilient experience.
The implemented flow, simplified
Content and progress live in SQLite.
Explain backup and cross-device benefits.
Apply referenced content and versioned preferences safely.
Deduplicate progress and preserve newer local changes.
Product interaction and engineering are designed together.
04Platforms & architecture
Expo and React Native share the native product across iOS and Android, including tablet layouts. SQLite makes bundled lessons and local progress available offline.
Supabase supports optional identity and account synchronization. Store purchase verification and entitlements stay server-authoritative.
Native iPhone and iPad product captures from the August 2026 store asset set, with staged learning content and no personal data. Staged content is not customer activity.
Bundled lessons and quizzes remain useful as a guest.
SQLite holds saved lessons, preferences and progress.
Authenticated Supabase synchronization connects the learner’s own devices.
The working stack
| Layer | Tools | Purpose |
|---|---|---|
| Native experience | Expo · React Native · TypeScript · Expo Router | Shared mobile and tablet navigation, screens and design primitives. |
| Local learning | Expo SQLite · Zustand · i18next | Bundled lessons, saved content, progress and localized interface state. |
| Cloud & commerce | Supabase Auth / Postgres / Edge Functions · StoreKit · Google Play Billing | Account sync, row-level ownership and server-verified entitlements. |
| Website & delivery | React · Vinext · Vite · EAS | A separate branded marketing site and native build workflow. |
Security is product work
Mondino has SOC 2 readiness documentation and implemented controls. This is not an independent attestation, certification or auditor opinion. Editorial coverage also does not imply independent cultural review.
SOC 2 is an independent examination of an organization’s controls against trust services criteria. Aligned controls and readiness work do not equal an auditor’s SOC 2 report, and “certified” would misstate our status. About SOC 2
Owner-scoped row-level security and authenticated sync protect account data.
Server verification checks purchases rather than trusting client-side payment state.
Security documentation covers privileged functions, secret checks, dependency reviews and incident / recovery procedures.
A managed platform helps with infrastructure; AS1 still owns application access, data policies, secrets and integration decisions. A provider’s SOC 2 report does not cover our application automatically. Supabase’s shared responsibility model
05Brand, marketing & distribution
We translated the product identity into a clear website promise: practical cultural context for real interactions, with short learning and offline access.
We connected identity, messaging, product education and acquisition. Conversion means helping the right visitor reach the next useful action, then measuring whether that action leads to value.
Visit the Mondino websiteCulture and situation guides create useful entry points. Descriptive metadata, canonicals, structured data and sitemap coverage support discovery beyond the homepage.
Authentic app previews, a concise learning journey and answers about guest access and offline use reduce uncertainty before the download. Both store CTAs remain visible.
We prepared the native product for iOS and Android distribution with branded store screenshots, listing content and direct website download links. The website complements the native app.
From discovery to first value
Discover a culture or interaction guide.
See a short lesson, quiz and offline behavior.
Choose the App Store or Google Play.
Reach a useful lesson before optional account creation.
We would connect guide engagement to store clicks and first-lesson completion, then return learning and purchase demand. Those steps need measurement before claiming improved conversion.
06Delivery & learning
We delivered the product system described here. Product-market fit has not been established.
These case studies show our ability to connect brand, product, design and engineering. The next stage is to establish adoption, paid demand and customer outcomes.
Structured around practical interactions.
A reusable lesson and practice framework.
Identity, content model, native product and backend.
What the build taught us
Offline behavior and account restoration are product decisions as well as engineering work. Reliability matters when learning needs to survive a lost connection or a change of device.
The next validation
We need to validate whether learners recall and use the guidance, return to saved lessons and see enough value to pay. Content breadth and engineering QA do not establish those outcomes.
The right team for the stage
We can take a product from idea to a working release, including its brand, frontend, managed backend and integrations.
The team model should evolve with the risk and demands of the business.
Before market fit is proven, scope and direction change quickly. Where appropriate, Supabase gives us a practical managed foundation. We can own application data models, authentication, backend functions and integrations while iterating on the product.
We recommend a lead responsible for data architecture, backend reliability, infrastructure and cybersecurity, working with AS1 on brand, product and design. Supabase may remain the right platform; scale calls for stronger engineering ownership, not an automatic rewrite.
Health-tech, fin-tech and other sensitive products: involve specialist engineering and security leadership from discovery. Data sensitivity, regulatory duties and operational risk can require that collaboration before market fit or rapid growth.
Your idea could be next
Bring us the problem, the people it serves and the stage you’re at. We’ll help shape a focused path from idea to product.
Discuss your project