Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)CH
Posts
1
Comments
121
Joined
2 yr. ago

  • Alright, so what extensions are you guys looking forward to? On mobile I don't think about it too much cause most of the websites I use on Desktop I use as apps on Android, so a couple of website specific extensions are useless for me

  • A bunch of design decisions only makes sense when viewed on a smartphone and even then, only after a little bit of usage.

    I remember I disliked Android 12 visual design when I looked at it through screenshots, but then absolutely loved it when I started actually using it

  • I really don't understand how so many apps get the default font size right, but Sync somehow appears to ignore system defaults or something? Like, I really like that it allows everyone to customize, but by default it looks like an app for ants

  • YouTube doesn't exactly use M3, it has some similarities, but it is pretty much its own thing. The bottom area on YouTube is also not exactly the same as the Navigation Bar from M3, the Create Button is very clearly not the same as the rest. In fact, the entire bottom area looks sort of similar to the Bottom App Bar from Material Design 2

    About YouTube Music and Google Podcasts. Yeah, they have an "Explore" option, but they work vastly differently from Sync, and it isn't even a matter of being a page vs bottom sheet. On Podcasts it works more like seeing the "Everything" feed than the explore sheet on Sync.

    I think Sync would benefit from removing the "Explore" option, and changing "Posts" to "Everything", and adding new targets from "Local" and "Subscribed" if they want to continue using the Navigation Bar.

    OR, they could swap it for a Bottom App Bar, and remove the "Posts" button, and treat the Inbox as being a subscreen rather than a main destination

  • Sorta...? Like, the outdated part is the visual, but the rest of the app is mostly fine, so you can spin the outdated visual as being minimalist or something like that. If you just updated the components to Material Design 3 it would be functional and fine.

    The same couldn't be said for Tasker for instance, which is outdated in general, and just updating the components wouldn't fix much of the issues it currently has with the UX.

  • That's honestly something I don't entirely get in the case of Sync. Like, there is nothing wrong with allowing users to tweak things, but Sync is like, really heavy on the Material Design 3, you look at it, and it is undoubtedly M3. Yet, there is always something odd about the way it uses it.

    Take for instance, the Navigation Bar, under Material Design Guidelines it is meant for destinations. And yet, on sync it offers:

    1. Home. A destination of sorts
    2. Explore. A button to open a bottom sheet
    3. Inbox. Also sort of a destination
    4. (optionally) Actions. Also a bottom tab

    The main FAB is also weird, as it isn't the primary action of the screen, it just opens a bottom sheet to bring more "actions" (some of which are destinations...)

    Like, Sync is a very good app, but it has a few odd things that are really weird.

  • I always thought Sync for Reddit looked cool, but never found myself comfortable with it because RIF existed, and I always felt more comfortable with it.

    I'm now using Sync and it is pretty great, but in my case it required some UI fiddling. It looks like Material Design 3, but I feel there's something wrong with the default values for font and text size nothing that is unfixable, but just... Weird

  • As far as I know, Flatpaks have the best foundation currently, there are a number of issues, but they are fixable and not entirely by design. And with Fedora Silverblue/Kinoite and OpenSUSE MicroOS you can really see how native debs/rpms/whatever isn't really that good of an idea for the average user and Flatpak is a solution to that.

    Appimages at a glance seems like a perfect solution for apps that for some reason or another needs to be kept outdated. But there is (was?) an issue of it not really bundling everything it needs, it looks and behaves as it is portable, but as far as I'm aware, it really isn't.

    And then there's Snap. Yeah, that one is just weird, it honestly just doesn't feel like a proper solution to any of the problems it tries to fix.

  • Hmm, I looked at the screenshots and didn't really like it. It somehow appears even more dated than RIF

    RIF was dated visually, but you could spin that as being minimalist and information dense. The Three Cheers for Tildes somehow doesn't look as dense and minimalist as RIF

  • Forking=/=Theming.

    Being open source does not make it easy to theme it. Reddit was closed source, but the tools to create a subreddit theme were far simpler than having to fork the actual visual code of reddit.

    There are also open source projects that allows you to edit just the visual files in a simple manner, for instance, KDE's Plasma is relatively simple to create new themes without having to fork the entire Desktop Environment, because it was made with theming in mind.

  • ...okay, that's a bit confusing but okay.

    I have two questions:

    1. Those web apps are made with theming in mind? One thing that Old Reddit allows is subreddits having their own css theme, some of them are better than the default old reddit. Suppose I'm the owner of a Lemmy instance and want to replicate the look of a specific reddit community, would that be a pain in the ass to do? The same question for Photon and Voyager, as I imagine some instance might want to further theme it, by changing things more thant just the banner and icon.
    2. Wouldn't it be better to write those interfaces as Lemmy-UI themes? Or is that impossible?
  • I remember the small outrage that happened when Google stopped officially calling Android versions by desserts. Nowadays I can't imagine going back.

    It was always weird because it only became clear with Android 6 (Marshmallow) and 7 (Nougat) that Google stopped making major versions with x.y numbers, with x.1 being exception. You couldn't just ask someone if they were on Android 4 cause there was at least 3 major Android versions, so it was easier to use the dessert names.

    It was also weird having to wonder if you should translate the dessert name when speaking casually about it.

  • Issue with that is that you need to stretch your finger to the top to show the screen in the first place. If you had to readjust your grip to reach the top, then you are likely already "in range" to reach the QS Tiles on top.

    If they moved the Quick Settings to the bottom, then you'd need to readjust your grip after triggering the Notifications/Quick Settings shade.

    It only makes sense to move the Tiles to the bottom if you also redesign how you trigger the shade

  • Spotty internet on both sides of the equation. It is common enough to happen.

    If your WiFi is weird at the moment due to ISP side maintenance, or if you are on the edge of the signal, you might want to disable wifi and enable mobile data.

    On the other hand, you could simply not have enough data left in your plan, so you want to keep your phone from using Mobile Data, even if you might get out of range from your router.