• 0 Posts
  • 44 Comments
Joined 1 year ago
cake
Cake day: July 14th, 2023

help-circle


  • A couple months ago, I logged into an old Reddit account. It only took a few minutes of scrolling before it happened.

    I had to scroll back up and try again, and record my screen so I could doublecheck my count later.

    35 ads or “recommended” posts (i.e. not from anything I subscribed to) in a row.

    I’m curious what that means for the overall percentage of the average user’s feed.

    Edit: Okay yall… I appreciate all of the free technical support, but it’s really not needed. I was just documenting some findings.

    But since everyone is so concerned about improving my Reddit experience, here are a few things to consider:

    • I’m a mobile dev, so I don’t mind enduring a shitty UX for the sake of finding out what other companies are doing with their apps. If I’m going in with a mindset of curiosity, it really doesn’t bother me. In fact, I want to see the worst parts.
    • Even if I had been going in just to have a pleasant scrolling experience, the reason I opened Reddit at all is because my wife had my phone for a while (due to toddler nonsense, we had swapped phones and she was stuck sitting in the hallway for a few minutes) and she had decided to open the app, so the decision of app vs. website was kinda made for me already.
    • Even if she had considered using the website instead, I wasn’t logged in because I only use private browsing (again, mobile dev, so when testing web flows I like to make sure there is no saved web data).
    • Even if I was already logged in, it’s an iPhone. While I do use an ad-blocker, the ad-blocking capabilities of Safari are pretty limited, so I’m not sure it would’ve improved much.
    • Even if I was on Android, I’d probably still not have any extensive ad-blocking enabled, because I want to stay relatively vanilla in my setup to reduce confounding factors when testing.
    • Even if there was a genuine opportunity here for my setup to be improved… I didn’t ask for that, and swarming people with “have you considered doing it the right way?” when they’re just making a basic observation doesn’t create a great atmosphere for the overall Lemmy experience.


  • I take it from your exasperation that you want a game to “just be good already”, from the very start. So I’ll exclude anything that takes too much thought or investment to start having a good time.

    • Deep Rock Galactic
    • Tunic
    • Pacific Drive
    • Gorogoa
    • Hardspace: Shipbreaker
    • Hand of Fate 2
    • FTL
    • Styx: Shards of Darkness
    • House of the Dying Sun
    • Hitman Go and Lara Craft Go
    • VVVVVV


  • Yearly refreshes make a lot more sense for phones, where the OS defines a lot more of the app lifecycle and common features, consumers might be interested in non-performance hardware upgrades like cameras, and things tend to be less spec-sensitive in the first place.

    For a gaming device, giving devs an uneven foundation and users a confusing compatibility matrix would spell doom.

    Edit: I should probably clarify that I wasn’t saying a yearly refresh for phones is good. Just that the context of Android+iOS is very different from the Steam Deck, and that context makes more frequent refreshes more attractive to consumers and less damaging to developers than it would be if applied to the Steam Deck also.

    Edit 2: I also just realized this is not the same story as the one a day or two ago that drew a direct comparison to phones. So I guess I should’ve gone back and commented on that one instead. I just wanted to share cuz I’ve had a lot of meetings about device support and consumer upgrade habits, as a mobile dev and as a game dev, and I don’t think most people would guess quite how different those two worlds are.


  • The Switch is ARM and uses several components from FreeBSD and Android. It would not be surprising to learn that they have the ability to compile system components like Virtual Console for an ARM Linux with stubs for Switch-specific stuff.

    The SNES Classic is also ARM, and has much less going on than the full Switch OS (Horizon). That could be the core of what they use for the museum displays, considering there’s an ARM version of Windows too.

    Either way, devs gonna dev. If you can’t get feedback at your workstation and always have to deploy to your target platform to test anything, you’re gonna move too slow to catch and fix bugs or build flexible enough systems to prevent them.

    So much of dev testing is about trade-offs between rapid iteration and thorough fidelity. You need access to both.

    From my own experience, I’ve done stuff like:

    • built mobile apps that can also be deployed as desktop apps or web apps for the sake of dev testing
    • built testing tools for car systems that fake out sensor input
    • built HTTP wrappers for cloud-deployed services to allow them to be run locally
    • faked out camera feeds for AR apps

    It can get janky, cuz not everything works the same way, but most of what you work on is not platform-specific anyway and a good architecture will minimize the portion of code that only works on the target platform.