Why Your Product Doesn't Need an App

The instinct is understandable: you sell a physical product, you want a digital relationship with the customer, so you build an app. The customer downloads it, registers their product, gets support, orders parts. The app is the hub.

In practice, most customers never download it.

Branded apps face a fundamental adoption problem. The customer bought a product, not a software subscription. They expect the product to work. They do not expect to manage another app alongside the dozens already on their phone. The result: low download rates, high abandonment, and a digital relationship that reaches a fraction of the installed base.

The App Adoption Problem

The challenge is structural, not marketing:

• Download friction. Asking a customer to find your app in the App Store, download it, create an account, verify their email, and then register their product is a multi-step journey most customers will not complete. Only 6% of consumers "always" register products (University of Michigan, 2015) even through simpler channels.
• App fatigue. Customers are selective about what stays on their phone. A branded app for a single product category competes for space against utilities they use daily. The maths do not favour a washing machine app or a power tool app.
• Platform maintenance. Supporting iOS and Android across device generations, OS updates, and screen sizes is an ongoing engineering cost. For a mid-market manufacturer, this is not core competency and diverts resources from product development.
• Gated experience. An app-only product experience excludes every customer who chose not to download it. If download rates are low, the majority of your installed base has no digital touchpoint at all.

The Web-First Alternative

A web-first product experience inverts the model. Instead of asking the customer to download software, you put a QR code on the product. They scan it with their phone camera (no app required) and land on a mobile-optimised web experience that knows their exact product.

The advantages are structural:

Zero install friction. The customer goes from physical product to digital experience in seconds, not minutes. No App Store, no download, no account creation before value is delivered. 87% of consumers say they would register if it was required to activate the warranty (UMich, 2015). QR-to-web removes the barriers that prevent this.

Universal reach. Every smartphone made in the last five years can scan a QR code natively. No platform dependency, no OS version requirement, no compatibility issues. The experience reaches every customer, not just the fraction who downloaded the app.

Lower cost to build and maintain. A web experience runs on a single codebase. No dual iOS/Android development. No App Store review cycles. No forced updates. Platform updates happen server-side and are immediately available to every user.

Instant context. A serialised QR code linked to the product database delivers a page that already knows the model, serial number, variant, and warranty status. The customer sees their product, not a generic portal.

What Customers Actually Need

When a customer interacts with a product digitally, they need one of a small number of things:

1. Setup help at unboxing (model-specific, immediately accessible)
2. Warranty registration (fast, minimal fields, instant confirmation)
3. Troubleshooting when something goes wrong (contextual, not generic)
4. Spare parts when something needs replacing (correct part for the correct model)
5. Warranty status check (is it still covered?)

None of these require a persistent app installation. All are better served by an on-demand web experience accessible from the product itself.

An app makes sense when the customer interacts with the product daily through software (smart home devices, fitness trackers, connected speakers). For products where the digital interaction is occasional and event-driven (appliances, tools, equipment, HVAC), web-first is the right architecture.

The Compliance Argument

The EU Battery Regulation requires battery passports accessible via a standardised identifier (QR code conforming to GS1 Digital Link). The ESPR extends Digital Product Passports to broader categories.

These regulations specify web-accessible data via a QR code, not an app download. A web-first product experience is architecturally aligned with DPP compliance. An app-first approach requires building the same web-accessible layer anyway to meet the regulation.

When an App Makes Sense

Apps are the right choice when:

• The product requires real-time interaction (smart home control, fitness tracking)
• Bluetooth or local connectivity is needed (tool configuration, sensor data)
• The customer uses the product daily through software

For everything else, a web-first product experience delivered via QR code reaches more customers, costs less to build, and aligns with emerging regulatory requirements.

---

BrandedMark delivers the connected product experience via web, not app. One QR scan connects registration, warranty, support, and spare parts with zero download friction. See how it works.