Java Spring Boot Backend for Mobile App

Mobile app of a retailer crashing under Black Friday peak loads? Or API responding in 5 seconds instead of 200 ms? Most often the root cause is a backend that can't handle concurrent requests, unoptimized database queries, or weak authentication. We build backends on Java Spring Boot that work stably under load up to 150,000 users. Our experience: over 50 implementations in fintech, logistics, and retail.

Why Spring Boot for mobile API works better than alternatives

Enterprise sector — banking, insurance, logistics. Here the mobile client serves as the frontend to business logic already running on Java. Rewriting it to Go or Node for "fashion" is expensive and risky. Spring Boot allows you to expose REST API on top of existing services in weeks, not months. Our engineers have experience migrating legacy systems to a microservice architecture while preserving contracts. Integration time savings reach 30% thanks to ready starters and configurations.

How to speed up Spring Boot application startup?

Standard Spring Boot 3.x starts in 8–15 seconds — this is a problem for Kubernetes under auto-scaling. According to Spring Boot Reference Documentation, GraalVM Native Image reduces startup time to hundreds of milliseconds. Alternatives: Spring WebFlux (reactive model with Netty reduces memory footprint) or simply keep at least two pods always running. The choice depends on load and infrastructure budget. Infrastructure cost reduction after optimization can reach 40%.

API architecture for mobile client

Stack: Spring Boot 3.x (Java 17+), Spring Data JPA + PostgreSQL (or MongoDB), Spring Security with JWT, Spring Cache + Redis, Spring Boot Actuator for health-check.

For push notifications use FCM via firebase-admin SDK or APNs via pushy library with HTTP/2 connection pool. WebSocket — through STOMP over SockJS for real-time features.

Case study: fintech app, 150,000 users, backend on Spring Boot 2.7. Endpoint /transactions/history with pagination regularly timed out. Reason: Hibernate loaded related entities with separate queries (N+1). After refactoring to @Query with JOIN FETCH and adding second-level cache (EhCache), response time dropped from 900 to 45 milliseconds. The mobile client stopped showing a loader for more than half a second. Operational cost decreased due to lower database load.

Typical endpoints for mobile API

Security and authentication

Spring Security 6 with SecurityFilterChain. Stateless authentication: JWT in Authorization header, refresh token in httpOnly cookie or Keychain. OAuth2 / Social Login — spring-security-oauth2-client supports Google, Apple (requires separate configuration of apple provider). For Apple, the non-standard flow with authorization_code and client_secret as JWT signed with ES256 is important.

Project structure

com.example.app
├── api         — controllers, DTOs, mappers (MapStruct)
├── domain      — entities, repository interfaces
├── service     — business logic
├── infrastructure  — JPA impl, Redis, FCM, S3
└── config      — Spring configuration

MapStruct for entity → DTO mapping generates code at compile time — no reflection overhead.

Deployment and operations

Docker image with layered JAR, Jib plugin for building without a Dockerfile. Kubernetes with readiness probe on /actuator/health/readiness and liveness probe on /actuator/health/liveness. HikariCP: maximumPoolSize calculated as (core_count * 2) + effective_spindle_count. For a 4-core instance with SSD, 10 connections per pod are sufficient.

What's included in the work

Development timeline

API with 15–20 methods, integration with one external system, authentication — 4–7 weeks. Full backend with realtime (WebSocket), notifications, analytics and CI/CD — 10–16 weeks. Contact us to discuss your project details and get an estimate. Request a consultation — we will analyze your task and offer the optimal solution. We guarantee operational stability and timely delivery.

Mobile App Architecture

The app is built in a single ViewController with 2000 lines. Network calls, business logic, UI updates—all in one place. Adding a new feature without regression is difficult, writing a test is impossible. This isn’t “bad code”—it’s a lack of architecture. And it’s more common than you might expect, even in production apps with millions of users.

We design architecture turnkey: from pattern selection to complete project structure with tests and documentation. In 7–10 days you get clean, modular code ready for scaling.

Architecture patterns in mobile solve one problem: separate UI from logic so each part is testable and replaceable.

MVVM: Basic Pattern

Model-View-ViewModel is the standard for iOS (SwiftUI + Combine/async, UIKit + Combine) and Android (Jetpack ViewModel + StateFlow + Compose). The ViewModel holds UI state and business logic. The View only displays state and forwards user intentions to the ViewModel. The Model represents data and its source.

Key rule: ViewModel knows nothing about UIKit or Android View classes. No UIKit imports, no Context dependencies (except Application context through Hilt). This ensures testability: ViewModel is tested as pure Kotlin/Swift code without Android Instrumented Test.

MVVM covers 70% of needs. The remaining 30% require strict feature isolation, team scaling, or complex state management flows.

Clean Architecture: When MVVM Isn’t Enough

Adds layers on top of MVVM:

• Domain layer — business logic, platform-independent. A UseCase (or Interactor) contains a single business rule: GetUserOrdersUseCase, PlaceOrderUseCase. Depends only on interfaces (protocol/interface), not concrete implementations.
• Data layer — repository implementations. OrderRepositoryImpl implements OrderRepository from domain. Knows about Retrofit, Room, UserDefaults. The ViewModel doesn’t know where data comes from—network or cache.
• Presentation layer — ViewModel + View. Knows about Domain, not Data.

Dependency rule: dependencies point inward only. Domain depends on nothing. Data and Presentation depend on Domain.

Presentation → Domain ← Data

This allows swapping implementations: tests use an in-memory repository instead of network, the interface remains the same.

Practical caveat: Clean Architecture adds files and layers. For small apps, this is overhead. It’s justified starting from ~15 features and teams of 3+ developers.

BLoC for Flutter: Predictable State Flow

BLoC (Business Logic Component) is the standard pattern in the Flutter community. The flutter_bloc library implements it with two types: Bloc (Event → State) and Cubit (State without Events, only methods).

Bloc processes Event and emits a new State via on<EventType> handlers. State is immutable—a new object for each change. BlocBuilder re-renders only the part of the tree where state changed.

// Event
abstract class CartEvent {}
class AddItemToCart extends CartEvent {
  final String productId;
  AddItemToCart(this.productId);
}

// State
abstract class CartState {}
class CartLoaded extends CartState {
  final List<CartItem> items;
  CartLoaded(this.items);
}

// Bloc
class CartBloc extends Bloc<CartEvent, CartState> {
  CartBloc(this._cartRepository) : super(CartLoaded([])) {
    on<AddItemToCart>(_onAddItem);
  }

  Future<void> _onAddItem(AddItemToCart event, Emitter<CartState> emit) async {
    final current = state as CartLoaded;
    final updated = await _cartRepository.addItem(event.productId);
    emit(CartLoaded(updated));
  }
}

The advantage of BLoC is testability. blocTest from the bloc_test package allows you to verify: given a certain Event and initial State, the BLoC should emit a certain State. No UI, no mocks for the Flutter framework.

VIPER: For Large iOS Projects

VIPER (View, Interactor, Presenter, Entity, Router) is the strictest separation of responsibilities for iOS. Each component has a protocol and concrete implementation.

• View — UI only, delegates everything to Presenter
• Interactor — business logic, network and data operations
• Presenter — mediator between View and Interactor, formats data for View
• Entity — data models (pure structures)
• Router — navigation between modules

Each module (screen or feature) is a separate VIPER module. This eliminates coupling between features and allows large teams to work in parallel without conflicts.

The cost: many files, many protocols. Boilerplate is generated via Sourcery or custom Xcode templates. VIPER is justified for apps with 10+ developers and 50+ screens.

TCA (The Composable Architecture)

TCA by Point-Free is a more modern alternative to VIPER for iOS/macOS. Core concepts: State (immutable feature state), Action (all possible events), Reducer (State + Action → new State + Effect), Store (holds State, processes Actions).

Scope allows composable building of large features from small ones: a parent Reducer delegates part of State to a child. Each feature is tested in isolation via TestStore with precise control over Effects.

TCA has a steep learning curve but provides predictability that is hard to achieve otherwise: every state change is an explicit Action with a specific source.

Which Pattern to Choose for Your Project?

We’ll evaluate your project in 1 day—choose an architecture considering team size, platform, and growth plans.

There is no universal answer. Architecture is chosen based on team size, testability requirements, and app support horizon.

What Components Are Included in Our Architecture Work?

• Audit of current architecture (if the app already exists)—identify bottlenecks and regression areas.
• Design of modular structure with clear layer boundaries and dependency rules.
• Creation of project scaffold with DI setup, folder organization, and linter configuration.
• Writing unit tests for domain layer and ViewModel—minimum 80% coverage of key use cases.
• Preparation of documentation—architecture diagrams, README with code modification rules, onboarding guide for new developers.
• Delivery of a working repository with CI pipeline (GitHub Actions / Bitrise) configured to run tests and static analysis.

All this is included in the design cost. Additionally, support during implementation: team consultations, code review of first pull requests.

How Does Lack of Architecture Affect Development Speed?

Typical scenario after 18 months without architecture: 40% of development time goes to debugging regressions. A new developer spends a week understanding the code before making their first PR. Tests aren’t written “because it’s hard to mock.” Adding a new feature requires understanding half the codebase.

Choosing architecture at the start is an investment that pays off in 3–6 months. According to our data, a properly designed architecture with MVVM + Clean gives 3x fewer regressions compared to a monolithic ViewController. And the cost of implementation is recouped in 2–3 sprints.

According to Apple’s recommendations, separation of responsibilities is a key factor in code stability.

Why Trust Our Team with Architecture?

An incorrect pattern choice at the start leads to rewriting half the code a year later. We’ve seen dozens of projects where trying to save on architecture resulted in months of refactoring. With over 10 years of commercial development experience and work on apps from 1 to 50 developers, we help avoid common mistakes:

• Overengineering for a simple MVP (we assign MVVM, not VIPER).
• Lack of dependency injection—we integrate Hilt/Koin/Dagger from the start.
• Ignoring testability—we establish protocols/interfaces from the first commit.

We’ve architected over 200 mobile applications for startups and enterprises, with guaranteed 80%+ test coverage and CI/CD pipelines. Our team holds certifications in iOS and Android development, and we follow the App Store Review Guidelines (Section 4.2/5.1) to ensure smooth store approvals.

Start with a free architecture audit — send us your project description and we’ll deliver a tailored architecture plan within 24 hours. Reach out via Telegram or email to get started.