Automotive & Retail

The Challenge

Double maintenance and marketplace reality

Dealers often maintain vehicles on marketplaces such as mobile.de and AutoScout24 while also needing a branded mobile experience. Manual copy-paste between channels wastes time, invites typos, and lets the showroom story drift away from online listings. The goal was to feed the customer-facing inventory from established import paths while still offering a dedicated app—without asking the dealership team to maintain every vehicle twice.

On-lot experience and uneven connectivity

Between forecourt, test drive, and workshop visits, mobile coverage fluctuates. If prospects decide on the lot, the app must not depend on immediate LTE. At the same time, pricing and stock should stay refreshable when a connection returns. The tension: fresh server-side truth via API, plus calm browsing through a cached catalog when the network is weak.

From physical vehicle to watchlist

Lots hold many vehicles; matching a real car to the right record should not take endless scrolling. A QR code on the vehicle bridges the physical context with the dataset: users land on the correct listing and can add cars to a watchlist. A "My car" area bundles upcoming inspection, MOT, and roadworthiness dates—retention beyond pure search.

Our Solution

App screenshots

Import-first instead of parallel entry

We designed the app so vehicle data flows from the marketplace import pipelines the dealership already relies on. Instead of re-keying stock in-house, the established feed remains the source of truth; the app formats listings for phones, keeps equipment and key figures readable, and aligns presentation with what arrives through the interfaces. Adjustments happen at integration and mapping layers—not through ad-hoc edits inside the app.

Startup sync and offline browsing

On launch the app checks via API whether new or changed vehicle data exists. When updates are available, users are offered a refresh—transparently, without opaque background churn. Cached inventory supports browsing without connectivity; when the network returns, newer data can be pulled. That combination fits real forecourt and travel scenarios without splitting online and offline into conflicting stories.

QR flow, watchlists, and "My car"

The built-in QR scanner connects the lot with the database: scanned codes open the matching vehicle, and watchlists support comparisons and sales conversations. The "My car" section lets customers maintain vehicles with upcoming service milestones—useful for loyalty and proactive communication beyond acquisition.

Delivery from East Frisia

Concept, implementation, and evolution are handled by Groenewold IT Solutions in Leer. We support such projects from interface and schema alignment through testing on common iPhones and Android devices—Made in Germany with short communication paths and clear ownership.

Results

One channel for stock and conversation

The app becomes a mobile channel that reflects the agreed marketplace inventory and supports on-lot conversations: less friction between online listings and face-to-face advice, clearer mapping via QR codes, and structured watchlists. For the dealership that means fewer mismatches to explain and a consistent baseline for sales follow-up.

Usability across connectivity

API-driven updates plus local cache address real-world conditions on the lot and on the move. Prospects are not forced to hunt for full bars before they can orient themselves; refreshes can follow when connectivity is back.

Maintainability

Architecture separates ingestion, presentation, and device capabilities (camera/QR). That allows import rule changes or extra fields to be introduced without rebuilding the entire client—a pattern we reuse across industry apps.

Data quality and marketplace logic

Consistent presentation

The app shapes imported vehicle data for smartphone reading. Key figures, equipment cues, and imagery stay traceable so prospects can compare quickly—without the dealership running a second editorial process for the app.

Updates with user control

When the API signals changes, an update is offered instead of silent background swaps. That keeps refresh moments understandable—important for data volume and expectations on mobile networks.

Engineering and collaboration

Technically the project follows the usual mobile pattern: imports and APIs provide authoritative data; the client handles formatting, caching, and on-device interaction. The split simplifies later extensions—e.g. EV-specific hints or regional campaigns—without tearing apart core logic.

Features

Feature overview

Import of listings from mobile.de and AutoScout24 to avoid duplicate data maintenance
Startup API check with prompt when new or changed vehicle data is available
Offline browsing of cached inventory
QR scanner to open the matching vehicle on the lot
Watchlist for favorites and sales discussions
"My car" area for inspection, MOT, and roadworthiness dates
Native iOS and Android apps
Customer retention and service information in one mobile surface
Delivery by Groenewold IT Solutions in Leer, Germany (Made in Germany)

Car Dealership App – Vehicle Listings, Marketplace Import & Offline Browsing