I have been able to backport some flutter iOS apps to 32bit legacy devices. This is only in some cases where all their dependencies are compatible + some tweaking of build scripts.

I wonder if Voyager can be backported, as it’s crossplatform (react native?) app. Before I dig does anyone know if this is possible?

EDIT: I’m not asking the devs to do anything, I’m asking anyone familiar with the code if they know whether this is feasible before I start digging

  • @aehardingM
    link
    English
    81 year ago

    Unfortunately not on iOS. I wish Apple did something like Android in this regard, where you can update the in-app webview independent of the OS. For example, you can run a quite old version of Android with newest Webview so you can run Voyager just fine.

    Maybe Apple will decouple Webkit updates and OS updates someday. ¯\_(ツ)_/¯

    • @cheese_greater
      link
      English
      2
      edit-2
      1 year ago

      I hope you don’t mind my little bit, I can take it down below if you prefer

  • @cheese_greater
    link
    English
    41 year ago

    He’s doing and continues amazing work so that might end up with you needing to consider pivoting to a more recent device as opposed to him unless he shares your passion for older devices/compatabillity etc 😊

    Edit: what about the PWA wefwef, could that possibly work for your usecase?

    • @[email protected]OP
      link
      fedilink
      English
      31 year ago

      Wefwef doesnt work, as it needs a newer webkit version to run. Legacy devices are completely left out of lemmy except for mlmym web app (which mirrors old.reddit).

      • Bloody Harry
        link
        fedilink
        English
        21 year ago

        if the wefwef PWA doesn’t work, I’m almost sure a Voyager build won’t work either, because they share like 95 % of their code base, and Voyager is also strongly dependent on recent-ish WebKit versions.

        • @cheese_greater
          link
          English
          11 year ago

          Ya, he’s gotta upgrade if this is important to him, open-source people doing this work need to be able to do their current and future work and not necessary worry about accomodating every device in existence :/

      • @cheese_greater
        link
        English
        1
        edit-2
        1 year ago

        I understand, but he’s gotta look forward. We all have to work together and understand each other’s challenges and unfortunately, its actually doable and far more so for you to upgrade regardless of any budgetary constraint.

        There’s plenty of older generation “new” phones (iPhones) to look at and I really hope you find one that works for you, if its refurbished its even cheaper. Check Amazon :) for the deal$

        Edit: What model is it, out of curiosity?

        • @[email protected]OP
          link
          fedilink
          English
          21 year ago

          I’m using voyager on my iphone just fine. This is for my old ipad (ipad 4, iOS 10.3.4).

          I have built some flutter apps with an older version of xcode & flutter and they work just fine. Guess it was worth a try asking here.

          • @cheese_greater
            link
            English
            1
            edit-2
            1 year ago

            I mean, you’ve been advised and empathized with so I think thats kinda it. Never hurts to ask as long as you’re able to hear something that differs from the ideal :)

            Edit: if thats a laudable goal, maybe you can try rebuilding it for that. He’s gotta focus on current and future, like ask his permission or I don’t know how that works but maybe he’s open to it

  • meseek #2982
    link
    fedilink
    English
    21 year ago

    It’s not React, it’s built on Ionic: https://ionicframework.com

    Moreover, it’s a web app, perfectly capable of running in Safari, even on older devices. Use a browser on older devices. Problem solved.

    • @aehardingM
      link
      English
      41 year ago

      Voyager is React and Ionic :)

      • body_by_make
        link
        fedilink
        English
        21 year ago

        They meant it’s not react native, which somebody else suggested.