We built Palabra from brand to backend: a personal language-learning product connected to teacher, school, sponsor and internal administration tools.
Explore the work01The opportunity
Learners want vocabulary that matters to them. Teachers need to turn it into useful practice. Schools and sponsors need access management. The people operating the platform need a safe way to support all of them.
We designed an ecosystem around a shared learning model and distinct responsibilities. A learner, a teacher and a sponsor should each understand their own workspace without navigating the complexity of the entire platform.
How could we connect personal learning and institutional workflows without giving everyone the same access?
The website explains learning and routes each audience.
Personal words become lessons and activities.
Classes, school seats and sponsored access support learning.
A privileged portal supports content, billing and service operations.
02From zero to one
We shaped the idea, created its identity, designed the experience and built the system that makes it work.
A connected learning ecosystem. The product choices, visual language and architecture developed together. Our research combined product, domain and technical exploration to shape the decisions below.
We framed personal vocabulary as the product core, then separated learner, teaching, school and sponsorship responsibilities.
We mapped language workflows, role boundaries, lesson delivery, seat assignment and payment failure cases into connected product requirements.
We created the Palabra identity, pixel wordmark, expressive illustrations, warm palette and a recognizable learning language.
We designed playful learner activities and denser operational interfaces, with consistent vocabulary and clear permission boundaries.
We built the Expo learner application plus dedicated React web apps for teachers and school staff, sponsors, and internal administrators.
We connected Supabase identity, scoped records, lesson delivery, language services, entitlements and payments, alongside the marketing website.
A complete brand identity
We built a playful learning identity that can stretch into serious operational tools. Recognition comes from shared characters, color and visual grammar, while each role gets the right level of density.
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.
We made a learner’s own vocabulary the starting point for lessons and practice. The same learning material can move through word cards, learned text and activities, rather than becoming a separate content silo for each exercise.
Personal input requires more careful content processing and recovery than a fixed course. It makes the lesson model reusable across personal and teaching contexts.
Teacher and school workflows share a dedicated application. Sponsor organizations have their own seats and recipients. Internal support has a separate privileged portal. These experiences connect through backend identity and data rules, not unrestricted visibility into each other’s information.
Multiple apps add coordination work. Clear responsibilities make complex access and administration easier to understand and govern.
We designed support and operations around learners, schools, organizations, lessons, deliveries, billing, provider monitoring and audit activity. A rich consumer experience needs operational tools that explain what happened and help staff respond safely.
Internal tooling takes time away from visible learner features. It provides the control needed to operate an interconnected service.
04Platforms & architecture
Palabra combines a learner app, teacher and school administration app, sponsor organization app, internal admin portal and website.
Expo and React Native share the learner foundation across web, iOS and Android. The operational portals use dedicated React interfaces suited to their different workflows.
The shared backend connects identity, learning and access. Role-specific data boundaries keep a sponsor workspace different from a school workspace or a privileged admin session.
One brand. Clear routes for every audience.
Personal words, lessons and practice
Classes, students, staff and seats
Sponsorship, recipients and access
Connected workflows with role-specific permissions and scoped data.
Support, content, deliveries, billing, monitoring and audits.
October 2026 browser captures of the full original applications running locally. Screens, navigation and styles are preserved; account content, learning content and operational data are staged or synthetic. Learner phone and tablet images show the actual responsive web app, not native-device captures. Counts and activity are illustrative, not business results.
Discovery leads into personal vocabulary, lessons and practice.
Schools manage classes and seats; organizations sponsor recipients.
Scoped identity and records connect the system; privileged operations stay in a separate portal.
The working stack
| Layer | Tools | Purpose |
|---|---|---|
| Learner experience | Expo · React Native · TypeScript | Shared learner components for web, iOS and Android. |
| Operational apps | React · TypeScript · Vite | Teacher and school workflows, sponsor organizations and the internal admin portal. |
| Data & access | Supabase Auth · Postgres · Edge Functions | Scoped workspaces, learning records, delivery, permissions and server-owned entitlements. |
| AI & language services | Gemini · OpenAI · Azure / Google translation | Gemini generates lessons; OpenAI supports fallback and review. Translation services and device speech connect language content to practice. |
| Commerce & delivery | Stripe · Apple / Google billing · Resend · Netlify · EAS | Verified payments connect seats and entitlements; transactional email supports delivery. Web frontends and native builds share the product identity. |
Security is product work
Palabra explicitly follows a SOC 2 Security Alignment checklist without a certification track. Some controls require ongoing operational work. We describe implemented safeguards and readiness, not independent attestation or blanket compliance.
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
Authorization and data policies separate learner, school, sponsor and administrator responsibilities.
Server-side administrator authorization, MFA requirements and audit trails support sensitive operations.
Access reviews, secret and dependency checks, incident procedures and recovery runbooks make security part of delivery.
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 used the same playful identity to explain personal vocabulary as the missing connection between finding a word and practicing it.
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 Palabra websiteLocalized learner, school and organization routes, pricing and explanatory pages use page-specific titles, descriptions, canonical URLs, structured data and sitemap generation.
Learner, school and sponsor entry points lead to different applications. Product education, examples and pricing support the decision before sign-up, without sending every audience through the same funnel.
The learner is available through web and native store routes. Teachers, school staff and sponsors enter their dedicated web tools. Store assets, listing copy and the website share the brand identity.
From discovery to first value
Personal learning, classroom teaching or sponsored access.
Understand vocabulary, lessons and practice.
Enter the learner, teaching or sponsor app.
Practice a lesson, assign learning or activate access.
We would measure conversion separately by persona: lesson activation, teacher assignment completion and sponsored learner activation. The website’s role is measurable acquisition and clearer expectations.
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.
Learner, teaching / school, sponsor, admin and website.
Web, iOS and Android share an Expo foundation.
Brand, product system, design and engineering.
What the build taught us
Complexity needs clear boundaries. A coherent ecosystem comes from a shared model, explicit roles and operational visibility as much as a consistent visual identity.
The next validation
We still need to establish repeat learning, classroom adoption and sustainable paid demand. A connected ecosystem demonstrates delivery capability; it does not by itself prove market fit.
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