Mobile Architect Kit
Design mobile apps and their backends: app architecture, BFF, API contract, threat model, app security testing and release.
8 templates in 3 steps, in the order you use them. Open any template in the editor, fill it in and export it to PDF, DOCX or HTML.
Design
Mobile App Architecture Template
FullMobile app architecture: native vs cross-platform, MVVM/Clean layers, offline sync, secure storage, auth, privacy, releases, testing
OWASP MASVS v2.1.0; RFC 8252 (BCP 212)Mobile Backend Design Template (BFF, Sync, Push)
FullBFF, screen-shaped APIs, native-app OAuth (PKCE, DPoP), offline sync and conflicts, APNs and FCM v1 push, old versions, rate limits, MASVS
RFC 8252 (BCP 212); RFC 9700; OWASP MASVS v2.1.0REST API Specification Template (OpenAPI 3.2, RFC 9457)
FullHTTP/JSON API contract: auth, conventions, QUERY, streaming, pagination, RFC 9457 errors, endpoints, webhooks, OpenAPI 3.2 skeleton
OpenAPI 3.2.1, RFC 9110, RFC 9457Notification Service System Design Template (Reference Design)
FullPush, email, SMS and in-app: templates, preferences and opt-out, priority queues, caps, provider failover, retries, dedup
RFC 8058; RFC 9989 (DMARC, May 2026); Netflix RENO case studyFile Sync System Design Template (Reference Design)
Full45-minute path, content-defined chunking, per-account dedupe, commit protocol, journal cursors and push, three-tree conflict handling, failure modes
LBFS content-defined chunking (SOSP 2001); public Dropbox engineering write-ups (cited)
Security
Threat Model Template (STRIDE)
FullSTRIDE threat model: scope, DFD with trust boundaries, assets, threats per element, L x I rating, mitigations, risk acceptance
STRIDEMobile App Security Assessment Template (OWASP MASVS 2.1, MASTG, MASWE)
FullApp scope, MAS profile choice (L1, L2, R, P), method, attack surface, 8 MASVS categories with MASWE and MASTG IDs, 24-control matrix, findings, retest
OWASP MASVS v2.1.0; MASWE v1.0.0; MASTG v2.0.0