Product design
Microapp Platform Manager
I framed app management as a product-control surface: discover what exists, understand status, configure permissions, and maintain platform modules from one place.
- Company
- Ultimate Knowledge Institute
- Industry
- Education Technology
- Role
- UI/UX Director
- Year
- 2020–2023
Project context
Case narrative leads with the challenge and problem solved.
The education platform had multiple microapps, operating states, and reusable patterns competing for attention. Users needed one place to understand what existed, what each app controlled, and where to act next. The case is intentionally text-led for now, focusing on challenge, constraints, decisions, and problem solved.
Case opening
Platform UX, admin tooling, information architecture, reusable education-product patterns, and design-system leadership.
- What was broken
- A modular education platform needs one clear place to understand what apps exist, what each app controls, and how reusable patterns across many tools stay coherent.
- What I owned
- I treated App Manager as the control layer for the broader microservice platform: app discovery, configuration, permissions, setup states, and reusable education-microapp patterns in one place.
- What changed
- The case emphasizes the challenge of making app discovery, setup, permissions, health, and launch behavior legible from one control layer.
Turned app management into a governance layer where discovery, setup, permissions, reporting, and launch states can be reviewed independently.
Product clarity index
What this case teaches.
- Handoff stabilized
- Library, setup, permissions, reporting, and empty states become reviewable modules.
- State clarified
- Platform owners can see what exists, what is configured, and what needs action.
Platform owners needed to understand many microapps, operating states, setup needs, and permissions without hunting through tools.
Frame App Manager as a governance layer for discovery, setup, access, reporting, empty states, and launch readiness.
Screens separate library, table, configuration, reporting, setup, navigation, and empty-state decisions into reviewable states.
Ownership / workflow
What I owned in the product story.
This is the platform/design-systems case: a modular education ecosystem needed governance, setup, permissions, reporting, and status patterns in one control layer.
- Role
- Platform UX, admin tool architecture, design-system thinking, interface direction.
- Scope
- App library, management tables, configuration detail, setup forms, reporting, permissions, navigation, empty states.
- Tools / workflow
- Figma product states, reusable admin patterns, governance model, component and data-region planning.
- Hiring signal
- Can create scalable product grammar for platform teams and internal tools.
Challenge / response / outcome
How Microapp Platform Manager became a clearer product flow.
A modular education platform needs one clear place to understand what apps exist, what each app controls, and how reusable patterns across many tools stay coherent.
I treated App Manager as the control layer for the broader microservice platform: app discovery, configuration, permissions, setup states, and reusable education-microapp patterns in one place.
The product challenge became an information-architecture problem.
- I treated App Manager as the control layer for a modular education platform: app purpose, status, permissions, setup, health, and launch behavior all needed a clear place in the interface.
- I separated library, table, configuration, reporting, setup, navigation, and empty-state views so each operating state could be reviewed and improved on its own.
- I used reusable setup sections, field groups, permissions, and review states so education tools could share a platform grammar instead of drifting into disconnected product behaviors.
- I kept the system practical for routine ownership: scan what exists, understand current state, configure the module, then launch or maintain it without leaving the product context.
What to notice
Interface decisions that prove the product thinking.
- Control surfaceMake app purpose, ownership, permissions, and launch state visible from one management layer.
- Operating statesSeparate library, setup, reporting, review, and empty states so each can be evaluated clearly.
- Platform grammarUse repeatable configuration patterns so microapps feel like one ecosystem.