We're looking for a senior web developer to help build the future of publishing. Work with a small team that's backed by incredible investors, build products that are used and loved by authors in over 100 countries.
It's really easy to publish an infinite amount of books on the Kindle store; I haven't tried iBookstore but I guess it's not very hard either (and do we need to care about them? What's their market share?)
I'm not ready to pay someone to just sit between me and the Kindle store; and I certainly won't surrender any royalties for this.
There are things in your presentation that do sound interesting, though:
- early feedback as the book is being written (that could maybe result in good word-of-mouth marketing)
- "incredible" sales reports
But in any case, I think the pricing should be more inline with DistroKid ($20 annual flat fee, 100% royalties, infinite amount of titles).
That's much better– I came to comment on the same thing. The people with fewer titles are the ones who need the royalties much more so than anyone else so the current pricing comes across as a hedge on one small author blowing up rather than developing an ecosystem which benefits all small authors. I imagine down the line there are many more services you could offer in exchange for royalties that would make sense– the analytics are one except they're very helpful at the base level too. Perhaps an additonal layer/finer grained analytics, a featured catalog, other promotional services, etc...
I like it a lot. Lots of potential for versioning.
I feel any real load could kill the server though (or your AWS budget!), so maybe trigger the save when I stop typing for half a second. Seems to lag a little when I type quickly.
I'd like to be able to save certain URLs as different versions to share. Could come in handy for collaboration or editing too.
The plan is to eventually use websockets ("magic") instead of foolishly POSTing, but is it possible that watching 'input' is the real mistake here? Perhaps I should just save every two seconds (or half second, as you suggest).
What would you suggest about saving urls? I couldn't think of anything easier than just bookmarking.
With each new URL you could store the previous ID and use that to build out a chain. It might be fairly expensive to do that dynamically, but there's no reason you couldn't serialize all of the previous IDs in a single column.
IMHO POSTing is fine, but you definitely want to wait a couple seconds each time.
I'm thinking really hard about this and I can't find anything I've shared that suggests I'm looking for a new payment gateway. Hence the post :)