REST API dla aplikacji mobilnej
Wersjonowane REST API z OAuth2, kolejkami i dokumentacją Swagger dla klienta iOS/Android (250k+ użytkowników).
- Branża
- Consumer mobile (iOS + Android)
- Czas trwania
- 4 months + ongoing
- Moja rola
- API architect
- Client
- Consumer mobile startup (250k+ MAU)
Wyzwanie
A consumer mobile app with 250k users was outgrowing a Firebase backend — query costs were exploding and the team couldn't enforce complex business rules. They needed a versioned, well-documented REST API that mobile clients could consume safely across multiple app versions.
Rozwiązanie
Designed a versioned REST API (`/v1`, `/v2`) on Laravel with OAuth2 (Passport) for auth, queued jobs via Horizon for heavy lifts, idempotency keys for mobile retries, and an OpenAPI 3 contract that doubles as the SDK source. Postman + Newman in CI catches contract drift before deploy.
Stack technologiczny
Rezultat
P95 latency under 180ms, zero auth incidents in 18 months, mobile teams ship faster because the OpenAPI contract removes ambiguity, and the Firebase bill dropped to a tenth.
Kluczowe metryki
- 250k+
- active users
- P95 < 180ms
- response time
- 100%
- OpenAPI coverage
Senior-level engineer who actually communicates. Our API project shipped two weeks early and passed security audit on first try.
