Ogni volta che passo davanti a questa pizzeria ad Abano Terme (PD) sono leggermente triggerato dal nome e dal logo ๐ง
Ma le ricette saranno open source?
@Thomas I would go for something like that: allowing users to choose whether they want images always loaded automatically (as-is), never loaded automatically (on demand) or when on WiFi networks.
Is this closer to what you expected?
Today I realized how similar RFL and RFL look at the surface: bottom navigation with identical sections, navigation drawer, a timeline in the home screen, each post with header, content, media, actions.
They look like an elder and a younger brother. But there are some differences too:
- RFL uses SQLDelight for persistence, whereas RFF uses Room multiplatform;
- RFL uses Voyager's Bottom sheet navigator, RFF plain Material3 ModalBottomSheets;
- RFL uses coil2 for image rendering on Android and Kamel on iOS, RFF uses coil3 for both platforms;
- RFL makes heavy usage of the slide-to-reveal pattern for like/dislike actions, RFF doesn't and do not allow dislike (even if on Friendica it could be technically done);
- RFL has many customization options (zombie mode, different post layouts, many more languages etc.), RFF tries to have "sane defaults" and has a more minimalistic approach;
- RFL has a "sidebar" on the right side which RFF does not have (again, minimalism);
- RFL does not use a third party crash reporting and feedback system, RFF uses Sentry;
- RFL has Android-only tests even for common code using MockK, RFF has common tests using Mokkery.
Have you tried both apps? Is there any feature of one app that you would like to be ported on the other one?
#fediverseapp #mobileapp #mobiledev #androiddev #kotlin #multiplatform #compose #opensource
v1/apps
) and then it opens the web page in the browser. Things can either go wrong in the first step (the post call) or whether the browser can not be opened. I'll add more error messages in a future release.