Core User Experience
Our app architecture is built for performance and retention. Unlike simple “wrapper” apps, we render the most important steps of the customer journey—browsing, searching, and product details—using Native Technologies, while offering special features designed to reduce friction.
1. Design & Navigation
Consistent Design (EDS)
Both the Mobile Webshop and the App are built upon the Empiriecom Design System (EDS).
- Consistency: UI elements—Buttons, fonts, colors, and spacing—are identical between Web and App.
- User Trust: Customers instantly recognize your brand environment, regardless of the device they use.
Navigation Structure
We rely on a modern, dual-bar navigation concept optimized for current iOS and Android standards. We do not use a “Burger Menu” (Off-Canvas), as data shows that visible navigation significantly increases engagement.
- Bottom Tab Bar: The anchor of the app. It provides one-tap access to the main views: Start, Categories, Wishlist, My Account, Cart.
- Top Navigation Bar: Contains contextual tools that are always available, like the Search and the Inbox.
2. Architecture: Native vs. WebView
We use a “Hybrid” approach: The areas where users spend 90% of their time are built natively for speed, while process-heavy areas use secure WebViews.
| Feature | Technology | Description |
|---|---|---|
| Storefront | Native | The start page. Content is managed in Drupal, but rendered natively for best performance. |
| Product List (PLP) | Native | Browsing categories. Includes native filter logic and sorting. |
| Product Detail (PDP) | Native | Unlike many other apps, our PDP is 100% Native. This includes the gallery, reviews, and the “Installment Calculator”. |
| Search | Native | A native modal overlay. Connects to the Empiriecom Product Search (or external providers). |
| Wishlist | Native | Fully native. Syncs automatically with the webshop. |
| Login & Account | Native | The Login, Forgot Password, and the “My Account” start hub are native. |
| Checkout & Basket | WebView | The entire purchase flow is a WebView. This ensures compatibility with all payment providers (PayPal, Klarna, etc.) without needing constant app updates. |
| Content Pages | WebView | Landing pages (except Storefront) and sub-pages like “Order History” or “Size Tables”. |
Why Native Matters (The Conversion Uplift)
Investing in native views for the main shopping funnel (PLP & PDP) is a strategic decision for growth.
- Speed: Native views load data instantly and allow for smooth 60fps scrolling, which feels much more responsive than a browser.
- Impact: Industry benchmarks (e.g., from major e-commerce platforms like the Otto Group) have shown that moving from a WebView PDP to a Native PDP can result in double-digit conversion rate uplifts. Users simply buy more when the experience feels premium and fast.
3. Development Strategy & Flexibility
The “Triple Implementation” Challenge
Because we build truly native experiences, a new feature affecting the Product Detail Page must technically be implemented across three platforms: Mobile Web, iOS, and Android.
- Our Solution: Thanks to our shared Empiriecom Design System (EDS) and agile processes, we coordinate these changes efficiently.
- Deployment: Please note that native changes require an App Store Release (iOS/Android), while Web changes are deployed instantly. We synchronize these release cycles tightly.
The “WebView Fallback” Option
We offer a unique flexibility feature for complex migrations or special requirements.
- Switching Technology: We can technically configure the app to load a specific view (e.g., the PDP) as a WebView instead of the Native View.
- Use Case: This is useful for temporary workarounds—for example, if you launch a highly complex new product configurator on the web that would be too expensive to rebuild natively immediately.
- Recommendation: We treat this as a fallback. We strongly recommend sticking to the Native implementation wherever possible to avoid the risk of losing conversion/revenue due to slower performance.
4. Key UX Features
Beyond the visual structure, the app offers specific behaviors designed to increase Customer Lifetime Value.
Persistent Login (“Forever Logged In”)
Unlike mobile websites, which often log users out for security reasons after a session expires, our app maintains a persistent user session via secure tokens.
- Benefit: Once a user logs in, they stay logged in virtually forever. This dramatically reduces the barrier to purchase.
- Note: Because the session never expires, we deliberately do not implement FaceID/TouchID for standard app entry. This removes an unnecessary interaction step.
Real-Time Synchronization
The biggest frustration for users is a disconnected experience. Our platform ensures 100% real-time synchronization between the App and the Web Shop.
- Cart Sync: An item added to the cart on the desktop is immediately visible in the app.
- Wishlist: “Favorites” are synced instantly when the view is opened.
- Account Data: Address changes or order history are always up to date.
Smart App Ratings
High store ratings are crucial for visibility. We use the native In-App Review API (Apple & Google).
- Smart Trigger: We don’t annoy users while they browse. The rating prompt is triggered only after a successful checkout (at the “moment of happiness”).
- Result: This significantly increases the ratio of 5-star reviews compared to random popups.
System-Native Voice Search
Instead of building a custom tool, we leverage the advanced capabilities of the operating system.
- Integration: Users can use the microphone button on the native iOS/Android keyboard to dictate search terms.
- Privacy: This respects the user’s system-wide privacy settings and offers better recognition quality than custom solutions.