Here are the problems I want to solve:
The same app everywhere
It will run as a website, iOS app (also on macOS), and Android app. It will be responsive, supporting phone, tablet, and computer screen sizes along with everything in between.
And I’m not talking about simply resizing the interface. Navigation (e.g. sidebar or on mobile bottom tab bar) will match what you would expect to see on the device size you’re using. But everything else (e.g. posts) will look the same, which I hope will make it really easy to jump from mobile to desktop.
Onboarding and configuration
The app will allow you to configure it to look like a typical Reddit or Lemmy app. During the onboarding process, I will prompt you, asking which style of interface you prefer. Consider these presets, which change a bunch of more granular configuration options. I will also give you the ability to fully customize each option instead of picking a preset.
Caching and offline support
This is where it starts to get more tricky. Caching is easy. If you launch the app, it will have everything you previously saw still loaded.
I would like to make it so upvoting, for example, can be done offline. The app will optimistically apply the upvote to the post or comment, then when you reconnect to the internet, it will actually apply the upvote. This is a difficult problem to solve, so I can’t promise this will work, and it would likely be the last feature I add.
I need your feedback
This is a big project to undertake. I really want a Lemmy client that checks those boxes for myself, but I’m curious if any of those resonate with you? Is there anything I missed that you would like to see? If I do build this, I will likely have to keep the project very focused as far as features go initially.
Just for context, I’m using Voyager on iOS currently. I really like it, but the “the same app everywhere” concept and making it easier to onboard Reddit users are my main motivations for creating my own app. My app will also be fully open source
at least the image resizing topic has recently been fixed in lemmy, thumbnails sizes are limited (at the time of thumbnail creation) in the latest release. I'd have to look closer at the other stuff, the api part is unlikely to have changed and will affect all frontends, but js part should differ depending on the front end. some instances already use other frontends by default and there is also a replacement for lemmy-ui being worked on (lemmy-ui-leptos), but I don't know how they compare. either.
it should be taken into account though how much of this is cacheable as well, as it will then typically only affect the first load for the static files.
I can totally understand the issues in general though, I've been living with a 64kbps uplink for several years in the past.
All good points. I also don't know how much is cacheable, but regardless, how much of that actually is cached, vs. being sent again and again?
Separately from the per-page considerations, from what people are saying it seems like a great deal of unnecessary info is sent along with each and every post that could be delayed until the user decides that they actually do want the additional info to make it worthwhile to pull in from the backend.
Yes some apps may also be lightweight, and perhaps PieFed could do a comparison with them as well, but to some degree that's an apples to oranges comparison (hehe, yet both are different kinds of fruits! and one may indeed find themselves in a position needing to choose between them at a grocery/market:-), seeing as how a web based UI needs to run in multiple browsers yet conversely runs from any OS.
If leptos also ends up being lightweight then it could be compared to PieFed at that time in that regard. Though atm all that PieFed can compare itself against are things available to be tested. And perhaps leptos will borrow a few tricks from PieFed by that time, or even if providing an entirely independent execution, could solve some of the same issues. Do you know if leptos is supposed to share that feature of being lightweight, or were you just saying that it will exist at some point?