3 ms·
Here's some feedback: * You should figure out a way not to require the payer to choose a password. Especially if they're already choosing a password on my serv
by shazow 15y ago
Here's some feedback:
* You should figure out a way not to require the payer to choose a password. Especially if they're already choosing a password on my service, now they're choosing two passwords. I understand that you're using this to handle plan changes and cancellation.
* Allow people to sign up for "free" products, too. This could potentially allow people to completely delegate their pricing pages to you, and you could be involved in the upsell process.
* Allow some formatting in the plan description. Specifically, I want to list things, which looks difficult to parse with a bunch of commas.
- gpl1 15y agoExcellent points. We will definitely consider these features going forward. Thanks!
- aaronblohowiak 15y agoI suggest markdown as a trivial to implement, useful, and safe template language.
- ZoFreX 15y agoA good idea :) You could also look at Textile, which is similar.
- johndbritton 15y ago+1 on handling free subscriptions
- deleted 15y ago[deleted]
- pwim 15y agoMy business partner and I were talking about a service like this the other day. If PintPay was to act as an OAuth provider, it might resolve the password issue.