RE: Let's Talk About Fees & Functionality Coming in the @tippy Text-to-Tip Service!
I would not include to many functions at launch, these will be better determined by the feedback you'll getting from the users. More functions also makes it more complex. Better to spend time on making the backend work in a resilient manner :) But that is just my 2cents :)
I could implement that command structure if you'd like. Anything is possible.
You may keep what you have now, but be prepared to change it. All depends on how many mistakes that users are gonna make. An idea could be to create some browser plugin that helps creating the command; ie a little menu to include recipient, value and currency. But this has there own challenges + more work to create, so keep that as a possible extension sometime after launch, ie candidate roadmap feature. I would start with only Steem, keep it simple, see how the users like it. It also drives demand for Steem since post are payed out in SBD when selecting the 50/50% :)
I've basically got the beast tipping SBD / STEEM / Powering up STEEM / Handling Deposits / Balances / Fee forwarding and a handful of other things.
It's not actually that difficult to build a fully feautured tip bot. The hard part will come with bullet proofing it and integrating with the STEEM blockchain.
I can always allow both styles of tipping.. Not a big deal. Functionality is already built just need to change the triggers around a bit.
Correct! That I know of software engineering, features are usually easy, in my line of business we call this marketing stuff. The real stuff, stability, resilience, scalability, integrations with other system are the difficult parts. When done that right, with top level performance vs hardware resources, you enter the game of high value IT software for which millions of $ are requested from customers.