information.
8. Low administrative overhead. If the system requires us to manually log every item we consume, we'll stop using it.

**Where I'm currently leaning**

I've been looking at **Baserow** as a possible foundation: relational data, forms, views, and APIs, with the potential to build a simple front end for crew.

I've also come across NocoDB, Grist, NocoBase, and dedicated inventory applications like Grocy. I'm not married to any particular solution, and I'm not sure whether a general purpose database platform or a collection of specialized applications would be better.

**My questions for the community**

* What would you use as the foundation for something like this?
* Am I trying to force too many unrelated functions into one application? Would a shared database with separate front ends make more sense?
* Is there an existing open-source project that already solves a significant portion of this?
* What's the best approach to offline mobile use and synchronization without building a custom application from scratch?
* Are there any major architectural mistakes or hidden maintenance burdens I should avoid?
* If you were starting this project with limited development experience, what would you build first?

I'm very much in the planning stage. My goal is to choose a sensible foundation and build incrementally rather than spend months developing something overly complicated.

Appreciate any suggestions, criticism, or examples of similar setups!

https://redd.it/1x1wqxh
@r_SelfHosted