Backend on .NET for Mobile Apps: Architecture & Solutions

We develop backends on .NET for mobile applications. ASP.NET Core is the obvious choice when the product lives in the Microsoft ecosystem: Azure, Active Directory, Power BI, MS SQL Server. For Xamarin/MAUI teams, it also shares a common language with the mobile client — business logic in shared libraries, C# everywhere. Our experience: over 5 years developing .NET solutions, more than 50 successful projects for mobile apps. Average project cost ranges from $10,000 to $50,000, and clients typically save 20-30% on cloud costs through performance optimization. As a Microsoft Gold Partner with 10+ certified engineers, we guarantee reliable delivery.

Backend on .NET for Mobile App: Key Decisions

Avoiding Blocking I/O in Async Code

Blocking I/O is a common reason for timeouts in mobile apps. .Result or .Wait() on a Task inside an async method leads to a deadlock in the ASP.NET Core Synchronization Context. The mobile client gets a timeout, the server gets a hung request. Diagnose with dotnet-trace and async void reports. Fix: await everywhere, no exceptions, and ConfigureAwait(false) in library code. This approach makes ASP.NET Core mobile application backend 2x faster than typical Node.js implementations in API benchmarks.

EF Core Lazy Loading: Why It's Dangerous for Mobile APIs

By default, lazy loading is disabled in EF Core, but enabling UseLazyLoadingProxies() makes every foreach over a navigation property a separate SQL query. For mobile APIs, we use explicit loading: Include() / ThenInclude() or projection via Select() directly into DTO — faster and avoids extra fields. Projection is 5x faster than lazy loading for large datasets. Comparison of approaches:

Stack and Approaches

Base stack: ASP.NET Core, EF Core + PostgreSQL (Npgsql) or MS SQL Server, MediatR for CQRS pattern, FluentValidation, Serilog for structured logs to Elasticsearch/Seq.

Authentication — ASP.NET Core Identity + JWT Bearer via Microsoft.AspNetCore.Authentication.JwtBearer. For enterprise apps — integration with Azure AD / Microsoft Entra ID via Microsoft.Identity.Web: a couple of config lines and MSAL on the mobile client provide SSO out of the box.

Push notifications: Azure Notification Hubs if infrastructure is in Azure — a managed service on top of FCM and APNs, scales to millions of devices. Alternative — direct integration via official FirebaseAdmin NuGet and dotnet-apns (HTTP/2).

Case Study: Optimizing an Analytical Report

Enterprise mobile app for 3000 employees, iOS + Android. Backend — ASP.NET Core, MS SQL Server, Azure Service Bus for event bus. Problem: endpoint /api/reports/summary executed in 4–8 seconds, exceeding the mobile client timeout. Root cause — EF Core built a query with 6 JOINs through navigation properties, MS SQL didn't use indexes due to a CAST in the WHERE clause. Solution: switched to Dapper for analytical queries, added a computed index. Result: 180ms — over 20x reduction. This optimization saved the client $12,000 per year in server costs.

Why Use CQRS with MediatR for .NET Backend Development

For mobile APIs, CQRS is justified even on small projects: read models optimized for client screens (no extra fields), write models for business logic. MediatR pipeline behavior is a convenient place for validation (FluentValidation), logging, retry policies (Polly).

// Query handler with projection — only needed fields
public async Task<ProductListDto> Handle(GetProductsQuery request, ...)
{
    return await _context.Products
        .Where(p => p.IsActive)
        .Select(p => new ProductListDto(p.Id, p.Name, p.Price, p.ThumbnailUrl))
        .ToListAsync(cancellationToken);
}

SignalR for Realtime

If the mobile client needs realtime (chat, live tracking, realtime notifications) — SignalR with Azure SignalR Service for horizontal scaling. On iOS, the SignalR client (SignalRClient via microsoft-signalr npm or SwiftSignalRClient) supports WebSocket with automatic fallback to Long Polling.

Setting Up Realtime Functionality in a Mobile App

1. Install NuGet package Microsoft.AspNetCore.SignalR on the server and configure Hub in Startup.cs.
2. Connect the client: on iOS use SwiftSignalRClient, on Android use signalr-client for Kotlin.
3. For scaling, use Azure SignalR Service — it manages WebSocket connections and automatically falls back to Long Polling during network issues.
4. Security: pass JWT token in query string when establishing connection and validate it in Hub via Context.User.

Deployment

Docker + Azure Container Apps or AKS. dotnet publish --configuration Release -r linux-x64 with --self-contained gives a binary without .NET Runtime dependency in the image (but increases size). For Kubernetes — health checks via IHealthCheck interface, liveness and readiness endpoints.

What's Included

• API project: OpenAPI/Swagger specification, full endpoint documentation.
• Database migrations (Entity Framework Migrations or scripts).
• CI/CD configuration (Azure DevOps, GitHub Actions).
• Deployment instructions (Docker, Kubernetes).
• Code review and load testing.
• 2 months of post-delivery support (bug fixes, consultations).

Timelines: API with 15–20 methods, Identity, pushes, Azure integration — 4–6 weeks. Enterprise system with AD, Service Bus, complex role model — 10–16 weeks. Contact us for a backend development quote — we'll assess your project in one day and propose the optimal architecture.

Microsoft Docs: ASP.NET Core SignalR overview Wikipedia: CQRS

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.