Fragmented learning resources
Educational resources and question-based learning can be harder to access when they are separated across channels.
Back to projects
Project / 02Mobile applicationsCompleted development
MyMedik Mobile Application
A mobile application developed to support healthcare-related education and professional engagement within the MyMedik ecosystem.
Technology stack
FlutterDartSupabasePostgreSQL
01 / Project overview
What was built and why it matters.
The MyMedik Mobile Application brings together learning resources, question banks, professional events, notifications, and user-related functionality in a mobile product direction.
It is designed for healthcare education and professional engagement, with documented scope covering both learner-facing flows and administration-related functionality.
Background
Healthcare education activities can become fragmented across different channels. The project was initiated to explore a more accessible mobile experience for learning, events, attendance, and professional development activities within the MyMedik ecosystem.
The available project information documents the scope and technology direction. Individual production-readiness claims are intentionally left for later verification.
02 / Problem
The product need behind the work.
The documented problem space is kept close to the available project context.
Disconnected professional activity
Events, attendance, notifications, and continuing development need a shared mobile context.
Different user needs
Learners, professionals, and administrators require different flows inside the same product ecosystem.
03 / Objectives
What the project set out to achieve.
- 01
Provide an accessible mobile learning experience.
- 02
Organise educational resources and question-based activities.
- 03
Support professional events, QR attendance, and CPD-related workflows.
- 04
Create role-aware user flows for the documented product scope.
04 / Solution
A product direction shaped around the real workflow.
The documented solution brings learning, events, attendance, notifications, profiles, and administration into one mobile application direction.
The user experience is organised around task-specific flows so that a learner can focus on education while other roles can access their relevant product areas. The scope is documented; feature-by-feature production status still requires verification.
05 / Features and modules
The parts that make up the experience.
Requires verification
Authentication
Documented account access and user entry flow for the mobile application.
Requires verification
Role-based experiences
Documented scope for different user experiences within the ecosystem.
Requires verification
Question bank
Organises question-based learning activities for healthcare education.
Requires verification
Learning resources
Provides a mobile home for educational content and reference materials.
Requires verification
Events and QR attendance
Supports documented event participation and QR-based attendance scope.
Requires verification
CPD hub
Creates a dedicated direction for continuing professional development activities.
Requires verification
Notifications and profiles
Keeps users informed and gives them a place to manage their application identity.
Requires verification
Admin management
Documents administration-related functionality within the wider application scope.
Scope labels describe the available project documentation; they are not claims that every feature is publicly deployed or production-ready.
06 / Technology stack
Tools chosen for the documented product direction.
Mobile
Flutter
Cross-platform framework for the mobile application experience.
Dart
Application language used with the Flutter development direction.
Backend
Supabase
Backend platform included in the documented project stack.
Database
PostgreSQL
Relational data technology included in the documented stack.
07 / System architecture
How the documented system pieces relate.
The documented technology context describes a Flutter and Dart mobile client connected to Supabase and PostgreSQL. Authentication and individual feature readiness remain areas for verification.
Flutter + Dart
Cross-platform mobile application layer.
Supabase
Documented backend and application data service.
PostgreSQL
Documented relational data layer.
The exact authentication configuration, notification service, and production infrastructure are not published in the available project record.
08 / My role and contributions
The work I personally contributed.
- ↗
Developed mobile interfaces and documented user flows.
- ↗
Worked on backend integration and the application data direction.
- ↗
Implemented or explored authentication-related flows within the documented scope.
- ↗
Translated healthcare education requirements into a cross-platform mobile experience.
09 / Development approach
From product context to working direction.
Map user roles
Separate learner, professional, and administration needs before shaping the mobile flows.
Organise learning
Group resources, question banks, events, and CPD-related experiences around clear tasks.
Build mobile flows
Develop cross-platform interfaces with the documented Flutter and Dart direction.
Verify readiness
Treat production status of individual features as an explicit validation step.
10 / Engineering insights
Considerations behind the implementation.
Where implementation incidents are not publicly documented, this section records grounded engineering considerations instead of inventing debugging stories.
Engineering consideration
Role-aware mobile experiences
Challenge
A healthcare education ecosystem can serve users with different responsibilities and priorities.
Approach
The documented scope was separated into learning, professional engagement, profile, and administration-related flows.
Solution
A role-aware product direction creates clearer entry points without presenting every capability to every user at once.
Learning
Mobile product clarity often comes from reducing the number of decisions a user has to make per screen.
11 / Project outcomes
What the development work resulted in.
- 01
A developed mobile application supporting the documented MyMedik healthcare education ecosystem.
- 01
A cross-platform product foundation for learning resources, events, question banks, and professional engagement.
- 01
Production readiness of individual features remains subject to verification.
12 / Project gallery
A place for verified product visuals.
ASSET PLACEHOLDERMobile screenshots will be added later
Mobile screenshots will be added later
Real device screenshots can be added without changing the case study layout once approved assets are available.