The inventory app that outgrew 50k reads
My test-hardware inventory app hit Firebase’s 50k read limit. I priced switching to an off-the-shelf tool (64 h) against moving to my own API (40 h), and moved it. It has been used company-wide since June 2026.
R&D and QA have a lot of test hardware, and every device is identified by its IMEI. I built and run the inventory for it: Expo / React Native for Android, iOS and web, an Express API, MongoDB, a C++ scanner service, Docker and GitLab CI. So far that’s at least 33 tickets and about 356 commits.
It started as a small tool and grew into a company-wide service.
Outgrowing Firebase
The first version went live on GitLab Pages the same day it was asked for. Then it moved to Firebase. When it hit Firebase’s 50k read limit, it needed a new home.
Before rebuilding, I priced the alternative. Moving to an off-the-shelf open-source asset manager came to 64 hours. Moving my app to its own backend came to 40. So I moved it to MongoDB behind my own Express API.
Scanning etched codes
The app reads QR and DataMatrix codes with zxing-cpp in three places: a Kotlin module on Android, WASM in the browser, and the scanner service on the server. Laser-etched codes are hard to read, so the decoders try several scales and inverted images.
I also added a server-side photo decoder (OpenCV, Tesseract OCR, zxing). It reads every code on a PCB from one photo, and does it better than the live scan.
Everyday use
Search supports AND/OR, exact (=) and partial (~) matching, suggestions and shareable filter links. Excel import and export puts each location on its own sheet. Device details fill in automatically, duplicate IMEIs are rejected, and devices can be reserved and released. There’s a daily backup, and admin mode has a git-like change history with revert.
An API for CI
The firmware CI pipeline needed the device list, but the app only had interactive single sign-on. So I built a separate machine API for CI, with its own credentials. CI firmware builds now use it to fetch their device list.
Webhooks are signed with HMAC, responses carry ETags for 304s, and a test catches the OpenAPI docs falling behind the routes.
Conclusion
Sorting 2,640 devices went from 487 ms to 92 ms. The app has 352 Jest tests and 1,371 screenshot comparisons. In June 2026 it launched company-wide, with company single sign-on.
Pricing the off-the-shelf option was worth it, even though I didn’t take it. 40 hours against 64 made it a decision, not a preference.