Web app is working and I use it daily. Two things left on my list before I would call it launchable: team accounts with shared workspaces and invites, or a React Native app so people can log entries away from a desk. Six hours a week, eight weeks, one person. I cannot do both and I keep flip-flopping weekly, which is itself costing me time.
If someone forces you to keep one: teams. Team accounts change who is able to pay you — a manager with a company card and four seats is a different customer from an individual with a personal one. Mobile mostly changes convenience for people who already decided to use it. And a responsive web app covers most of what people mean when they say they want an app.
Mobile is not a feature, it is a second product with its own release cycle, store review, crash reporting and a build that breaks when an SDK deprecates something. On six hours a week it will consume all six for months, and the first submission alone can eat weeks of your eight.
The calendar part is underrated. Even when everything goes right, review plus a rejection plus a resubmission is not compatible with an eight week deadline you also want to build in.
Estimate both in hours, double the estimate, then check the total against 48. It will not fit and the decision makes itself. The flip-flopping is happening because you are comparing them as ideas rather than as hours.
Where does the eight weeks come from? If it is arbitrary, that is the cheapest thing on the list to cut.
@leech_wrangler · 9mo ago · 2 replies
Cut both.
Forty-eight hours is one feature, badly, not two. Ship the single-user web version and put both of them on the page as a "which of these do you need?" question with an email box. You will get an answer within a fortnight of launching that is worth more than either implementation, because right now you are choosing on the basis of what you imagine users want.
Also, launchable is not a property of your feature list. It is a property of whether one person can pay you.
Reply
Report
@lena_arbogast · 9mo ago
Did this. 42 people ticked teams, 3 ticked mobile. The mobile one was obviously the one I wanted to build, which is presumably why I had it on the list.
Reply
Report