This week I started testing Amatino with real people: Friends foolish enough to give in to my begging. The only thing ready for them is the sign-up process, there is a whole bunch of wiring up needed before they can interact with much else.
Nevertheless, even in just the sign-up process, the feedback came in thick and fast. Lots of little things that I would not have noticed, but other people do. So, I jumped in and changed a few things:
- Added a password length requirement hint (thanks Andrew!)
- Added warning about junk mail / Gmail Promotions (thanks Andrew!)
- Tightened up application blurb wording (thanks Tim!)
- Added prominent ‘subscribe’ button on home page (thanks Jessica!)
- Insert ‘set username’ as the first option on account activation (thanks Jessica!)
Baby steps, right? Meanwhile, in the background, I’ve been attacking the billing system. The Amatino Api expects looks for a valid subscription before it responds to a request. At the moment, subscriptions made at https://amatino.io aren’t wired up to the billing database.
Before I make the link, I need to flesh out a bunch of boring but important billing interface elements: Change payment method, cancel subscription, change subscription type, and so on.
There is an argument to be made that this stuff is not “Minimum Viable Product”, but in my mind, ease of control over a subscription is absolutely core to Amatino. I absolutely rage out when services don’t make it easy to cancel, change, or update the way in which I pay them my hard-earned money. To that end, changes I just pushed to the Amatino Web application include:
- Added https://amatino.io/billing/change-subscription page
- Wrangled some details in the subscription relational data model
- Abstracted various subscription billing objects currently used at https://amatino.io/subscribe, so that they can be used in other billing interfaces