Overview & Architecture Pattern
Mobile JWT authentication with token refresh, FCM/APNs device registration, delta sync timestamps, and optimized payloads.
Architecture Pattern: Web & Mobile
Primary Use Case: iOS and Android companion APIs, offline-first mobile sync architectures, push notification delivery.
Included Dependencies & Starters
spring-boot-starter-web, spring-boot-starter-security, data-jpa, postgresql, validation
Domain Entities & Scaffolding Defaults
MobileUser (email, phone), DeviceToken (userId, platform, token, appVersion, lastSeen)
Quickstart: Running Your Project
# 1. Start required infrastructure containers
docker compose up -d
# 2. Run the Spring Boot 3.4 application (Maven)
./mvnw spring-boot:run
# Or run with Gradle
./gradlew bootRun
Frequently Asked Questions
- What starters are included in the Mobile Application Backend blueprint?
- The Mobile Application Backend blueprint includes spring-boot-starter-web, spring-boot-starter-security, data-jpa, postgresql, validation, pre-configured application.yml properties, and production-ready connection pools.
- How do I run the generated Mobile Application Backend project locally?
- Extract the downloaded ZIP, start dependencies with 'docker compose up -d', and execute './mvnw spring-boot:run' (Maven) or './gradlew bootRun' (Gradle).
- Can I customize entities and database schemas in this blueprint?
- Yes, SpringForge allows you to visually add or modify JPA entities, field types, validation rules, and relational mappings, or import SQL DDL schemas.