devShark
A learning platform for developers built as a real product rather than a UI demo. It combines structured learning content, quiz mechanics, progress tracking, and multiplayer functionality in a maintainable React and Supabase architecture.
- Context
- Independent learning product
- Role
- Product owner and full-stack developer
- Status
- Live product
- Platform
- React and Supabase
Problem
Developer-learning tools often separate content, practice, progress, and competition into disconnected experiences.
The product needed an architecture that could support structured topic paths, daily challenges, progress, leaderboards, and real-time multiplayer without becoming difficult to extend.
Constraints
As an owner-operated product, product decisions, implementation, deployment, and maintenance share the same limited attention.
Real-time features and user data require clear authorization and data ownership.
My responsibility
Defined the product structure and learning mechanics.
Designed the React application and Supabase data model.
Implemented authentication, authorization, progress tracking, and quiz flows.
Built real-time multiplayer and leaderboard behavior.
Own deployment, maintenance, and ongoing product decisions.
Approach
Separated learning content, attempts, progress, and multiplayer state into purposeful models.
Kept feature boundaries explicit so new topic paths and challenge types can be added without rewriting the core flow.
Used Supabase for integrated data, authentication, and real-time behavior while keeping application rules visible in the codebase.
Key technical decisions
Model learning progress separately from content
Content changes over time, while a user's attempts and progress need stable meaning.
Keep content structure and user progress as separate concerns connected through stable identifiers.
The learning model can evolve without treating content records and user state as the same thing.
Treat multiplayer as a product flow
Real-time transport alone does not define room state, transitions, reconnect behavior, or results.
Model multiplayer around explicit room and game states, with real-time updates carrying those state transitions.
Outcomes
Shipped and operate a live product at devshark.app.
Combined structured learning, quizzes, progress, leaderboards, and multiplayer in one product architecture.
Built a foundation that supports ongoing product and content development.
Reflection
Owning the product changes engineering priorities. Maintainability, operational simplicity, and what not to build matter as much as feature delivery.
Related work
Need someone who can own the boundaries?
I am open to selected product work and future senior engineering opportunities.
Contact me