Mobility & fleet apps (multi-package repo)
Vehicle Maintenance Platform
Offline Flutter car-maintenance tracker plus NestJS/MongoDB JWT API—same repo also holds an unrelated Wingz admin client and a Nest GraphQL form generator.
Background & Context
car-app-main is a multi-package repository: Flutter car-app (SQLite on device), NestJS car-app-server (/api/v1 auth, users, cars, maintenance, notifications), React car-app-client branded around catalog/CMS talking to external adminserver.wingzimpex.com (not the car API), and form-generator CLI for Nest GraphQL modules from JSON. Flutter does not call the Nest server; the React admin does not call the car API. No Docker/CI; Swagger module not registered; schedule/multer deps unused for cron/uploads.
Search demand around mobility & fleet apps (multi-package repo) and Vehicle Maintenance Platform keeps rising as operators look for proof—not slide decks—before they hire a build partner.
Tekvers framed Vehicle Maintenance Platform as a mobility & fleet apps (multi-package repo) engagement with clear module boundaries, measurable outcomes, and a stack centered on Flutter, Provider, sqflite, NestJS 11, Mongoose.
Delivery covered software development, ui ux design, cloud devops, with SEO-ready surfaces and internal linking so the public story reinforces the product work.
This case study page targets buyers researching mobility & fleet apps (multi-package repo) architecture, vendor evaluation, and implementation risk—paired with related Tekvers blogs and guides on the same niche.
The Challenge
Vehicle owners needed on-device service history and due-date organization; a companion API was also designed for multi-user ownership—without claiming end-to-end sync that source does not wire. Without a coherent mobility & fleet apps (multi-package repo) foundation, Vehicle Maintenance Platform stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The Solution
Vehicle Maintenance Platform: Offline Flutter car-maintenance tracker plus NestJS/MongoDB JWT API—same repo also holds an unrelated Wingz admin client and a Nest GraphQL form generator. On-device vehicle inventory and maintenance schema foundation. Tekvers delivered a maintainable mobility & fleet apps (multi-package repo) system for Vehicle Maintenance Platform using Flutter, Provider, sqflite, NestJS 11, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Our Approach
Offline-first mobile
SQLite keeps the garage usable without inventing a sync protocol the Flutter app does not implement.
API as companion domain
Nest models the same cars/maintenance concepts with ownership and analytics endpoints for future clients.
Repo hygiene in the narrative
Case study separates car product from Wingz admin client and form-generator tooling so reviewers are not misled.
What We Delivered
- Flutter maintenance tracker with Provider + sqflite
- NestJS 11 `/api/v1` cars/maintenance/users/notifications API
- JWT auth and admin-gated user management
- Maintenance aggregation and upcoming/overdue queries
- React TailAdmin client for external Wingz catalog API (separate product surface)
- NestJS GraphQL form code-generator CLI with examples
Outcomes & Impact
- On-device vehicle inventory and maintenance schema foundation
- Multi-role Nest API ready for authenticated clients
- Explicit non-claims: no mobile↔API sync, incomplete Flutter maintenance write UX (TODOs), no push delivery
- Clear separation of unrelated packages in the same repo
Owners can keep a durable local maintenance record; engineers get a Nest domain model for the same problem—Tekvers documents the architectural reality instead of inventing cloud sync.
Technology Stack
Services Delivered
Related Case Studies
Guides & articles from this niche
Planning a similar platform? Share your scope and we will map architecture, delivery phases, and a realistic timeline.