Quote:
Originally Posted by eschwartz
So I think it would be fair to say that whatever Marvin is now, that's what you're getting.
|
I'd be cautiously more optimistic.
Not as optimistic as to expect a Marvin for Android version, which is the subject matter of this thread – that really seems unrealistic, as things stand now.
My hope, however, is that one fine day, Kris will refocus his energies, once again pushing Marvin to the top of his priority list, instead of to the bottom where it resides now. I have no idea what the users' feedback to the Gerty and Sift apps may have been, but my guess would be, it likely wasn't 5% as enthusiastic as the reception Marvin got from users in late 2012. When Marvin came out, it was a
revelation. When Gerty came out... well, it was a journaling app, but there are better journaling apps out there (such as Day One). When Sift came out... well, it was a mail app, but there are better mail apps out there (such as Mailbox). You can't say the same thing about Marvin, though –
there is currently no better e-reader app on this planet than Marvin. I'm convinced that that's true, even though I'd only rate Marvin 3.5 out of 5 stars at this stage; yet nothing comes even close to Marvin on iOS, while on Android, Moon+ Reader does come close, but I believe it still lags behind Marvin, all things considered.
For these reasons, I'm convinced that Marvin – not Gerty or Sift – is the ideal "market niche" for Kris. The current corporate market leaders, Kindle and iBooks, are as crude pieces of software as it can get. Marvin could become the world's first professional-grade EPUB e-reader – suitable both for "regular folks" or avid book readers, and for literary scholars or others professionally working with literature.
But to get there, all those user feature requests and issues reported over at GitHub need to be accounted for. You can't oblige every feature request, naturally; but, at the very least, each feature request/issue report needs to be carefully considered. (Unfortunately, some have already been dismissed
without due consideration, in my estimation.) You can't just summarily dismiss all those dozens of issues reported by many, many Marvin users (not just myself) over the last few years at GitHub, and declare the product to be almost finished. Nope, it's not finished. Not by a long shot.
