How We Used to Think About Native Apps — and What Changed
This post was originally published in August 2024 under the title "Why Shelf Doesn't Have Native Apps." It now reflects what changed when we shipped Shelf Companion on the App Store. The URL is preserved so the conversation history stays intact. For the original arguments and what we'd say differently today, read on.
In August 2024 I wrote a post titled "Why Shelf Doesn't Have Native Apps." The argument was simple: progressive web apps were enough, native apps added overhead without proportional value, and our small team's energy was better spent shipping features than maintaining app store binaries.
In May 2026 we shipped Shelf Companion on the iOS App Store.
This is the honest story of what changed, what stayed true, and what we would say differently today.
What we said in 2024
The original post made five points in favor of PWAs over native apps: universal access from any browser, an app-like home-screen experience, no version fragmentation, fewer "the app was broken" support tickets, and modern browser APIs for camera and hardware.
All of that is still true. None of it was wrong.
What we missed
We underweighted the difference between good enough and purpose-built for the specific work field teams do.
Browser-based barcode scanning works for one-offs. It does not scale to an audit of 200 assets where every scan is friction. Camera autofocus, format support, haptic feedback, instant home-screen quick actions — small things individually, but in aggregate they change whether a tool gets used eight hours a day or abandoned for a clipboard.
We also underestimated how strongly people associate "this company takes field work seriously" with "this company has a native app." Even when the PWA technically did the job, the absence of an App Store presence read as a signal that field operations were a secondary use case. They are not.
What changed our mind
Three operational gaps that the browser could not close, all from real customer conversations.
Offline scan persistence. PWAs cache pages but cannot reliably queue writes and sync them later. A field team scanning 200 assets in a basement with no signal needs their work to survive the network gap. Native saves to the device, syncs on reconnect, does not lose work. The web could not do this.
Scanner performance at batch speed. Code 128, EAN-13, DataMatrix, audits at the speed teams actually work — browser scanning was too slow for sustained use. Native gets sub-second focus and recognition with haptic confirmation, so you can keep scanning without looking at the screen.
The trust signal. "Is there a mobile app?" came up in nearly every enterprise conversation. Even when our PWA answer was good, the absence of an App Store presence read as a gap. Shipping a native companion closed that gap honestly.
What stayed the same
The web app is still the source of truth. Workspaces, billing, configuration, bulk imports, custom fields, role management, reporting, integrations — all of that lives on the web. The companion does not replace the web platform; it complements it for the work that happens away from a desk.
The PWA still exists and still works. If you do not want to install another app, you can keep using shelf.nu in your phone browser. Adding it to your home screen still gets you a native-like experience, and we will keep maintaining that path.
Pricing did not change. The companion is free with any Shelf account, including the free tier. Nothing is sold through the app.
What we would say differently today
Two things.
First, the original post used "PWAs are the future" framing. That was overconfident. PWAs are a future for a lot of use cases, and they remain a strong default. "Always use PWAs, never go native" is a dogma we no longer hold. The right answer is task-specific.
Second, we framed the choice as binary — native or web — when in practice the strongest pattern is a focused native companion alongside a web source of truth. That is what we ship now and it works better than either side of the binary would have.
What is next
Shelf Companion is on the App Store (iPhone) and Google Play (Android) now. It is free with any Shelf account, including the free tier.
For the full feature breakdown of the companion app and what it is built to do, read Why We're Building the Shelf Mobile App.
Carlos Virreira Founder, Shelf Asset Management, Inc.
Ready to organize your assets?
Join thousands of teams who trust Shelf to manage their physical assets. Free forever, or try the Team plan free for 7 days.
Out in the field? Shelf Companion is free on iPhone & Android.
More from the blog
Take Control of Your Booking Notifications
Shelf now lets workspace admins configure exactly who receives booking email notifications — at both the workspace level and per booking. Reduce noise, add coverage, and keep the right people informed.
Industry-Specific CSV Import Examples
One of the most powerful features of Shelf is its ability to import existing asset data via CSV files. To help you get started, we've created a set of industry-specific CSV templates that you can use as a starting point for your own asset management journey.
New Feature Update: Streamlined Bookings and Calendar Integration
we've added an "Add to Calendar" button to the booking page for past bookings. This generates an ICS (Internet Calendar Subscription) file containing essential information about the booking, along with a link to the booking page. Now, you can easily add your bookings to your preferred calendar app or platform, keeping track of your schedule a breeze.