Website and mobile app sharing one API
FreeSystem map@rabbinatix/web-mobile-shared-architecture by Rabbinatixupdated Oct 13, 2026
One backend serves both a website and a phone app, so both must agree with it.
3 systems and 6 APIs. Every API is declared on both sides, so every contract starts healthy. Rename or change anything once it is on your map.
2 connections · 6 APIs
- Web App → Backend API
POST /api/v1/auth/registerCreate an accountPOST /api/v1/auth/loginLog in with email and passwordPOST /api/v1/auth/logoutLog outGET /api/v1/meThe signed-in userGET /api/v1/projectsThe user’s projectsPOST /api/v1/projectsCreate a project
- Mobile App → Backend API
POST /api/v1/auth/registerCreate an accountPOST /api/v1/auth/loginLog in with email and passwordPOST /api/v1/auth/logoutLog outGET /api/v1/meThe signed-in userGET /api/v1/projectsThe user’s projectsPOST /api/v1/projectsCreate a project
Systems (3)
Web App
The website.
Mobile App
The iPhone and Android app.
Backend API
Accounts and data for both apps.
A system you already have under the same name is used, not copied. Outside APIs don't count towards your plan.
Also as a flow
Versions
