Przejdź do głównej zawartości


The latest beta of Relatica mobile/desktop client for Friendica is now released: Version 0.1.0b3. Builds are ready for download or are in TestFlight for all platforms: iOS, Android, Linux, Mac, and Windows. New features include an image carousel for easily swiping between images, full paging in galleries to make load times easier on big galleries, being able to copy text out of posts, comments, post links, etc., and a new way of doing status and refreshing in timelines, galleries, and notifications. Bug fixes include fixing the systemic issue where Flutter apps on Android pre-8.0 devices not seeing LetsEncrypt certs as valid, some improvement on app icons (but looks uglier on later Android OSs), and some ease of use tweaks throughout. More details, install instructions, etc at below link. #relatica #friendica #fediverse : https://gitlab.com/mysocialportal/relatica/-/blob/main/CHANGELOG.md#version-010b3-beta
how do I join the TestFlight? Would like to test and suggest
If you have a Friendica account (or want to set one up on a server somewhere) then I can DM you a link to join.
Tried it first time and first impression is - damn, that thing so fluent!
Thanks! Glad you like it. UI/UX is very much a weak point in my skills but I’m hoping my dogfooding it all day helps overcome that :).
In that case maybe the best way is not to reinvent the wheel, but inspire yourself in existing stuff i guess
Yep look at stuff like that for guiedance etc. I've often found the way many of those are slapped together doesn't help as much with flow design etc although they can be great for getting hints on how to properly scale icons, image sets etc, as long as they are FOSS friendly anyway.
First comment from #relatica !
Overall good impression although I cannot find the timeline that corresponds in the web interface Network->Last activity (path: /network?order=commented)
I want to add that eventually but rebuilding that through the Mastodon API is very complicated/expensive since I get an amalgam of comments and posts with no real association. For every comment that didn't return the original post I have to do a second query to pull that. It essentially increases the number of calls to the server for every update by a factor of 10-50x. It's an artifact of Mastadon not really doing a threading view. We should be able to augment the Mastodon API to achieve that eventually at which point we could support that. I should probably add that as a bullet for something I want to implement in the nearer term.