I’m in a bit of a dilemma. On the one hand, there are a lot of things I want to add to Snapie Mobile—lots of features I’m excited about, lots of code I’ve already shipped. But I’m wondering if I’m breaking my own rules.
You see, when Snapie Mobile was born—when the idea was born, to be specific—what I wanted was a very simple, fun gateway to Hive, to crypto, to Web3. In that sense, Snapie was and still is stripped of many features normally found on Hive frontends. Anything that could be too intimidating: gone. The purpose always clear.
But it’s difficult, at least for me, to see the bare-bones feature set working well—mind you—and not feel the urge to add complexity to it. Yes, I added OpenPods, a simple take on them too, but I’ve not added games, nor the ability to write blogs, nor extended video uploads. The list goes on.
Today I began implementing Google logins to Snapie Mobile. It’s something that, in my opinion, is part of making Snapie Mobile the easiest app to use. But as I was doing that, scope creep began rearing its head.
“What if I add a full blog composer?” I thought—only to slap myself in the face, figuratively of course, and come back to the mission: simplicity.
How much is too much is the question. Yes, I added wallet features too, but even then, I may have already broken the plan. Maybe wallet features in Snapie Mobile is already too much.
The point is: I’m arguing with myself, and somehow both sides are losing.
— MenO