Mobile app package diagram
A mobile app package diagram shows the major modules in an application and how requests cross their boundaries. Presentation contains screens, domain contains use cases, data contains repositories, and network or platform packages hold external concerns. The arrows show direction: a screen invokes a use case, while the repository hides whether data comes from a cache or API. This is a concise way to discuss architecture in a design review before modeling the details of individual types.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
A mobile team documents the boundaries of an app feature.
Key decisions
- Separate UI: Screens depend on use cases rather than network clients.
- Keep domain central: Use cases coordinate application behavior.
- Isolate data access: Repositories hide cache and API details.
- Mark platform dependencies: Show push services at the outer boundary.
When to reuse this
Use when explaining a modular mobile architecture to developers and reviewers.
Frequently asked questions
Why separate domain from data?
Can packages contain many classes?
Should UI call the API directly?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.