Cloud-native architecture
Context
The situation before the platform
Why sign language learners needed one structured, Deaf-led place to learn instead of a browser full of tabs.
| The business |
A Deaf-led Educational Technology initiative, serving learners, instructors, and administrators across a growing community of Deaf and hearing users. |
| The starting point |
Online sign language education was fragmented. Learners pieced knowledge together from YouTube tutorials, generic language apps, Zoom classes, PDFs and scattered social content — most of it without a structured curriculum, consistent accessibility or authentic Deaf-led instruction. |
| The trigger |
Without a clear path to follow, learners could not track progress or stay motivated, and had few opportunities to practise with others — the one thing language learning depends on most. |
| What they wanted |
A unified, modern and scalable learning platform making sign language education available anytime and anywhere, while actively supporting Deaf culture, promoting inclusivity and building genuine connection between learners. |
| Constraints |
Sign language is a visual language rooted in Deaf culture, so accessibility had to shape the interface rather than decorate it · video needed to stream reliably across devices and connection speeds · the mobile app had to match the web platform feature for feature, not offer a reduced version of it. |
System
What it runs at today
A production-ready platform and mobile application, built for scale and long-term growth.
Deaf-led instruction
100 %
Course content created and delivered by Deaf instructors themselves
Backend modules
7
Authentication, courses, video, subscriptions, notifications, community and analytics
Engagement length
24 +
Months, with a dedicated product team and ongoing support
Team size
4 +
Covering web, cross-platform mobile, backend and QA
The engineering problem
Four gaps that shaped the platform from day one
Not vague pain points — the specific reasons learning sign language online kept breaking down, each paired with what we did about it.
0
1
Learning felt pieced together rather than guided
Learners jumped between random videos, documents and apps with no clear path to follow, which made progress impossible to track and motivation hard to sustain. Without a curriculum or a central platform, there was no sense of direction or consistency to build a skill on.
What we did
Structured learning paths with guided courses, clear module progression and lesson tracking, so every learner has one route through the material and can see how far along it they are.
0
2
Existing platforms weren't built for a visual language
sign language is visual and deeply rooted in Deaf culture, yet most platforms failed to reflect that in their experience. Poor visual communication design and the absence of Deaf-led instruction left content feeling neither authentic nor inclusive, limiting both understanding and cultural connection.
What we did
Accessibility as a core design principle rather than an afterthought — every interaction crafted to support visual learning, with content created and delivered by Deaf instructors so the language arrives with its cultural context intact.
0
3
Learners had nowhere to practise with other people
Language learning thrives on interaction, but sign language learners frequently studied alone. With few chances to practise, ask questions or hold real conversations, building the confidence and fluency that any language requires became far harder than it needed to be.
What we did
Dedicated spaces for discussion, live group sessions and real-time notifications, turning learning from a solo activity into a shared one where learners practise regularly and stay connected to instructors and peers.
0
4
Mobile experiences lagged behind their web counterparts
Learners expect to study anytime, anywhere, on any device. Existing sign language solutions fell short on mobile — either poorly designed or missing features the web version had — which left the experience feeling disconnected and frustrating across platforms.
What we did
A cross-platform mobile app built in Flutter, giving a consistent, near-native experience on iOS and Android from a single codebase, with APIs and content delivery optimized for fast, reliable playback.
Architecture
How it fits together
Simplified — the shape rather than every service.
0
1
CLIENTS
React.js web · Flutter · iOS Flutter · Android
One React web platform and a single Flutter codebase serving both mobile stores, so the learning experience stays consistent wherever a student opens it.
0
2
GATEWAY
Node.js API · Role-based access control · Secure auth & sessions
Requests pass through secure authentication and session management, with role-based access control deciding precisely what a student, instructor or administrator can reach.
0
3
SERVICES
Courses · Video handling · Live sessions · Community · Subscriptions · Notifications · Analytics
The backend is modular by design: each function is separated so it can scale on its own, and new features arrive without disrupting the rest of the platform.
0
4
DATA & INFRA
AWS · Firebase · GitHub CI/CD
Deployed to scalable cloud infrastructure with CI/CD pipelines automating testing and release, so updates ship continuously rather than in risky batches.
Separating authentication, courses, video, subscriptions, notifications, community and analytics keeps the system organised and lets each component scale independently — the reason new features can be introduced without touching the whole platform.
Solutions
Six systems doing the actual work
Not a features list — the specific things we built behind every number above.
One unified learning platform
Self-paced lessons, live classes, progress tracking, instructor interaction and community engagement in one place instead of several tools a learner has to switch between.
Video-based learning system
A structured, video-first system reflecting the visual nature of sign language — courses organised into clear modules with lesson tracking and responsive streaming across devices.
Community & engagement features
Discussion spaces, live group sessions and real-time notifications that encourage regular practice and let learners ask questions and connect with each other.
Subscription & e-commerce system
Premium memberships, secure payment processing, course purchases and recurring plans, designed so new pricing tiers and offers can be added as the platform evolves.
Deaf-led learning experience
Content created and delivered by Deaf instructors, so learners understand the language within its cultural context rather than memorising signs in isolation.
Accessibility-first product design
Every interaction crafted to support visual learning and inclusivity, keeping the platform comfortable and intuitive for both Deaf and hearing learners.
KEY FEATURES
What the platform does day to day
Five capabilities, each closing one of the gaps identified above.
| Capability | Runs | Refresh | What it does |
|---|---|---|---|
| Structured learning paths | CURRICULUM | Per lesson | Guided courses with lesson progression and progress tracking for every skill level |
| Live classes & instructor interaction | LIVE SESSION | Real time | Join live sessions with Deaf instructors, ask questions and practise signing as it happens |
| Video-based learning experience | STREAMED | On demand | High-quality video lessons with seamless streaming and tracking across web and mobile |
| Community & practice hub | COMMUNITY | Continuous | Discussion spaces and engagement features that connect learners with each other |
| Subscription & cross-platform access | RECURRING | Per cycle | Secure subscriptions and course access management, unified across web and mobile |
INTEGRATIONS
How the outside world plugs in
Live classes, payments and notifications reach the platform through the modular service layer rather than sitting beside it as separate tools.
EXTERNAL SYSTEMS
Agora
Live interactive class sessions
Stripe
Payments & recurring subscriptions
Firebase
Push notifications
GitHub CI/CD
Automated test & release
↓
THROUGH THE MODULAR SERVICE LAYER ↓
Platform integration layer
Node.js modules
One separated concern per service
Role-based access control
Students, instructors, admins
Notification pipeline
Real-time learner updates
↓
INTO THE CORE SERVICES ↓
CORE SERVICES
Courses
Video
Live sessions
Community
Subscriptions
Because every external system resolves into the same modular backend, a learner's subscription, course access, live class booking and notifications all describe one account rather than four disconnected records.
SECURITY
What protects learners, instructors and content
Security was treated as a core priority: course content is the product, and learner data sits behind it.
Role-based access control
A robust RBAC system manages student, instructor and administrator roles with precise permissions, so each account reaches only what it should.
Secure authentication & sessions
Secure authentication flows and session management keep accounts protected across web and mobile without making sign-in a chore.
Controlled content access
Access mechanisms protect course material and administrative tools, so premium video content stays tied to a valid subscription.
Validated deployments
The codebase is managed in GitHub with CI/CD pipelines automating testing and deployment, so changes reach production already checked.
PROCESS
How we got there
Five stages, starting with the people who teach and learn on the platform rather than a feature list.
0
1
Discovery & stakeholder mapping
Engaging the client team to understand students, instructors, administrators and the wider community, so features were grounded in real needs rather than assumptions.
0
2
Modular system architecture
A Node.js backend separating authentication, courses, video, subscriptions, notifications, community and analytics so each part scales independently
0
3
Security & access control
Role-based access control, secure authentication flows, session management and controlled access to protect data, content and administrative tools.
0
4
Performance optimisation
Flutter for a consistent near-native mobile experience from one codebase, with APIs and content delivery tuned for fast loading and smooth playback
0
5
Testing & deployment
The codebase managed in GitHub with CI/CD pipelines automating testing and deployment to scalable cloud infrastructure for continuous, low-risk releases.
BUSINESS IMPACT
What changed for the business
Beyond the headline numbers, three things learners and instructors noticed first.
From initiative to product ecosystem
A vision-driven educational initiative became a scalable digital platform, pairing structured learning paths with authentic Deaf-led instruction.
A community, not a course catalogue
Interactive and community-driven features improved student engagement, giving learners a supportive environment to practise in rather than a library to work through alone.
Scalable revenue model
Subscription-based access introduced recurring revenue that grows with the community, with room for new tiers and offers as the platform expands.
COMMERCIAL OUTCOME
What the engineering choices are worth in operating terms
Every headline number traces back to a specific decision, not a vague platform effect.
| ENGINEERING DECISION | OPERATING OUTOME | MEASURED EFFECT |
|---|---|---|
| Deaf-led, accessibility-first content system | Learners understand sign language in its cultural context, not as isolated signs | 100% Deaf-led |
| Flutter mobile app with feature parity | The same learning experience on web, iOS and Android | 95% device accessibility |
| Structured course paths with lesson tracking | One guided route replaces scattered videos, PDFs and social content | 90% structured coverage |
| Community spaces, live sessions & notifications | Regular practice with instructors and peers instead of solo study | 85% engagement enabled |
STACK
What it's built on
The actual technologies, not feature names with icons attached.
Frontend
- React.js
- HTML
- CSS
- JavaScript
Mobile
- Flutter
- iOS
- Android
Backend
- Node.js
Cloud & integrations
- AWS
- Firebase
- Stripe
- Agora
FULL CASE STUDY
Get the complete write-up as a PDF
The same content on this page, plus the extended module breakdown and delivery phases, in a single document you can share internally.
- Full platform and service architecture
- Discovery-to-launch process, phase by phase
- Accessibility and security decisions in detail
Download the case study
No spam • unsubscribe anytime • we’re here when you need us
More work
Other platform builds
Hospitality
Every stay, extraordinary.
Hospitality group transformed guest experiences through IoT-enabled room automation, reducing service requests by 58%
Hospitality group transformed guest experiences through IoT-enabled room automation, reducing service requests by 58%
IoT - Hospitality
Read the case study →