• kibiz0r
    link
    fedilink
    arrow-up
    6
    arrow-down
    11
    ·
    edit-2
    1 month ago

    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.

      • kibiz0r
        link
        fedilink
        arrow-up
        3
        ·
        1 month ago

        Yeah, that was my point.

        Because so much of a (typical) mobile app’s behavior is delegated to first-party APIs, having a huge range of device models in the field doesn’t cause as much of a splintering problem as it would for software that defines more of its own behavior internally, like games tend to do.