I love this sentiment. I built a beer inventory app exclusively for myself + guests picking a drink to try when when they’re over at my house. I’m up to 26 “users” over the past few years, but most of them just browse on my phone when they need another drink.
When I talk about the app, some people immediately jump to other inventory problems in their own lives: Can you make it work for my wine fridge? Could I keep track of my kids’ ever-changing wardrobe? I’d love to manage my Warhammer collection this way! It certainly seems like there could be a consumer product to help tackle those problems, but it’s not gonna be my app.
Edit: In more of a work context, I think internal tooling for specific users or teams can feel similarly empowering. When you have an intentionally-constrained set of users, finding product-market fit and making sure the solution actually works for their needs becomes the only goal. And with so few users, it’s easy to keep tabs on what is and isn’t working for them.
Is your app open source? If not, have you considered that? You could just say in the readme, "fork it if you want it to do something specific". Sounds like it could be a good starting point for a bunch of things. :)
> In more of a work context, I think internal tooling for specific users or teams can feel similarly empowering. When you have an intentionally-constrained set of users, finding product-market fit and making sure the solution actually works for their needs becomes the only goal. And with so few users, it’s easy to keep tabs on what is and isn’t working for them.
I've seen a few of these and they always fall into (non-)maintenance hell once the dev (it's always just one, because the business can't spare a whole team for something like this) leaves, or until the next re-org (read: almost certainly less than two years from any random point in time) when the responsibilities of the team it was built for are divided among other teams, or outsourced to a body shop like CapGemini that won't use it (because they can replace the functionality with an army of managers with spreadsheets, all of which they can bill for).
In short, I think it's largely a fantasy to develop custom software for small userbases on economic grounds (at least for nontechnical users using typical "real" stacks -- spreadsheets and "programmer tools" are a different story), which is kind of the point of this piece.
When I talk about the app, some people immediately jump to other inventory problems in their own lives: Can you make it work for my wine fridge? Could I keep track of my kids’ ever-changing wardrobe? I’d love to manage my Warhammer collection this way! It certainly seems like there could be a consumer product to help tackle those problems, but it’s not gonna be my app.
Edit: In more of a work context, I think internal tooling for specific users or teams can feel similarly empowering. When you have an intentionally-constrained set of users, finding product-market fit and making sure the solution actually works for their needs becomes the only goal. And with so few users, it’s easy to keep tabs on what is and isn’t working for them.