Gregory's ServerHonestly, Pinafore is the only interface I need for Mastodon, and the main one I've used since I started developing it. I know the Mastodon frontend has tons of features Pinafore doesn't support (trending hashtags, server announcements, profile editing, etc.) but I just haven't felt hugely motivated to add those.
|
6 comments
Originally, my goal with Pinafore was to build what I thought was the "ideal" Mastodon UI from a technical perspective. Fast, accessible, offline-first, single-column, true virtual list, etc. Since then, the Mastodon frontend has caught up in a lot of ways (e.g. single column), so these things are less of a competitive advantage. I also saw it as a way to push the limits of what the web could do. However, I've become a bit chastened and disillusioned about this. For instance: - Pinafore doesn't have nice animated transitions like native apps do. The web still sucks at this.  @Gargron I maybe overstated my case. A lot of it is not Mastodon's fault but just how hard it is to write offline-first apps in general. When I worked on PouchDB, we had a whole sync protocol between the client and server that dealt with versioning, conflicts, etc. You just called `db.sync()` and you were done. I don't expect Mastodon to add this, but it's just an example of the kind of thing I miss from the PouchDB world.  |
I'm conflicted between wondering if this is me just being chauvinistic, or if it's actually a low-key value-add for Pinafore that it doesn't have a million bells and whistles (which would probably make it slower, etc.). Maybe some users like a more stripped-down interface where the cheese doesn't move much?