← Back to context

Comment by desdenova

1 year ago

I wish it was feasible to have alternative mobile systems, but it's not really.

You can't simply give up every popular app for a system nobody else uses or develops for.

Sailfish has Android emulation, but good luck running banking apps without Google SafetyNet. Even pure Android ROMs, like LineageOS, can't do that.

Also good luck with proprietary firmware for mobile networking and cameras. Another thing that usually holds back AOSP distributions, and will likely be even worse in a non-Android system.

Today sure, it just needs support from a major player. Not -that- long ago, nearly every mfg had their own OS(Blackberry, Meego/Symbian, Win Mobile, Palm, etc) and each had enough apps.

If Samsung or Huawei or probably even Motorola decided to ditch Android and go all in on Sailfish, we'd see support for apps in short order. But as a third party OS you have to install yourself, it's basically dead in the water.

What BlackBerry did before giving up was a smart approach, they basically just converted Android apps to BlackBerry ones for you. And that'd be a fast way to get bootstrapped. They just didn't have enough steam left in them, sadly.

  • > each had enough apps.

    They had enough apps in the same way 640k of RAM was enough for everyone.

    I think it's a fantastic topic, but to be succinct: we couldn't get app makers to keep parity between iOS and android, including banks, government and transportation apps for a very long time.

    Assuming it would go easier with a random 3rd OS where "I'm sued for illegal deals" Google has struggled so much doesn't sound realistic.

    • > They had enough apps in the same way 640k of RAM was enough for everyone.

      It pretty much was, for almost everyone, for quite a few years.

  • BlackBerry was a huge player. They declined, as with Nokia, entirely because they didn’t use a platform

    • Well, their problems were manifold and I think the movie does a decent job explaining them. Highly recommend, if you haven't seen it yet.

      They didn't evolve, took the iPhone as a joke, and when finally playing catch-up, the hardware was awful.

      If they'd have seen the writing on the wall and responded in kind, I think we'd have all three players around today.

      Nokia...I don't even want to talk about. I'm still half convinced it was a sabotage job.

      4 replies →

  • Sailfish is the successor to Nokia's Linux efforts, before they scrapped it all for Windows.

    • The community got fractured when the N9/950 did MeeGo Harmattan. This was a continuation of Nokia's Maemo OS that was based on Debian, but they just called it differently when they announced a collaboration. Nokia and Intel started a 'merge' called MeeGo (based on moblin and fedora). Nokia never actually used this in a device as they signed the famous partnership under Stephen Elop's guidance standing on a burning platform.

      Sailfish is a successor of this actual MeeGo work that was done and therefore had an uphill battle. They never got the same traction as Maemo (or even Mer), so I never called this a successor of Nokia's work. Nokia created a community with developer conferences and handing out devices. Jolla couldn't do this ... and therefore remained niche.

      2 replies →

But for an old phone a very open and developer friendly environment (Linux like maybe) is attractive. Sadly those available are limited to more modern phones, which is I think a mistake. Maybe the answer is a side loaded application with a ridiculous amount of permissions?

> You can't simply give up every popular app for a system nobody else uses or develops for.

Perhaps the solution for such a phone is to make PWAs feasible for every kind of app?

I guess it would need a few essential built-in apps (something like an Apple Health analog) but hopefully the rest could be web apps with extra privileges, if needed and approved by the user.

Is geofencing already possible with PWAs? I.e. location based events? If not, that would also have to be a builtin (helper) app.

Yep, if you capitulate from the start than nothing changes. And you as a user are giving them a chance to lock you into custom OTPs (that are just little changed standard OTP to force you to use their app so they can track you, steal your contacts and god knows what else (i have reversed it, got the seed and i am running it from shell as I was sick of it) even if they have a classic web page.

Everyone just agreed that it is fine if certificates are no longer used for web apps (even with a fully standardized pkcs#12 tokens), everyone just agreed that bank is using some non-standard otp generator, everyone just agreed with everything. Now you will soon have to pay heating in car on monthly basis.

Stop agreeing. Start complaining. Now and you.

Sailfish on Sony Xperia 10 works like a charm, with working things that even modded roms are having issue with.

If you fight it back... I am running my banking app (that they have even if they also have a web based app) for 4 years now without any issues, they did a major rewrite in between, but quite frankly in most of cases Safety-net is just a bunch of sand into eyes of security, if implemented right it might have impact but at the end most of banking banks are reducing it to if statement (that i patched).

Yep, true that normal user cant do this, but this is users call. Complain to financial ombudsman, complain to the bank, demand a way for you to authenticate if you are paying for the product, complain bank supporting phone monopoly etc.

Harass developers that decided to verify if phone is rooted, prove in media that they are just a bunch of kids having a boner on security they don't understand (which is a huge fact in all annoying login schemes, from mail to sms etc., OTP was more than enough (sms... giggling... ss7 access on tor for 500 dollars monthly)

Actually you are addressing wrong problem. It starts somewhere else, when you want to use Bluetooth hardware that has a custom app to use it and you cant use it on Sailfish while you cant use it in Android layer as there is no bluetooth pass-trough. Here I vote with my wallet, not buying such devices and waiting for Sailfish to implement it.

Does it have good messaging and maps? That’s 90% of my phone usage. I don’t do banking on my phone.

  • It has outstanding offline maps and navigation. One of its strongest points.

    Messaging support depends on the protocol. Very good for Telegram, good for Matrix and Signal.

    Lots of people use e.g. WhatsApp through the Android emulation layer.

> I wish it was feasible to have alternative mobile systems, but it's not really.

I think there is a possible exception here.

I mean, firstly, yes, sadly this is largely true.

I had a Blackberry Passport, a beautiful handset running the QNX-based BB X OS. Over a year of ownership it gradually got less and less useful as app vendors turned off BB X support. No FB IM, no Whatsapp, and I have a phone that won't let me text with 90% of the most-contacted people on my phone.

And in those days (2014-2015) I did much less with my phone than now.

But I also own 2 little-used tablets.

I use tablets for watching films and TV, reading books, occasionally email. I don't do any of the mobile-phone stuff on my tablets, and they do not have SIM cards in them.

I would have as much use for a FOSS-powered tablet as I do for an Android or iOS tablet.

Poor patchy phone support does not cut it, sadly, and that's more than doubly so without apps.

But good support for at least one currently-available cheap Chinese tablet would be of legitimate interest to me.

> good luck running banking apps without Google SafetyNet.

Doesn't most banks have a mobile version of their website. Maybe not the best but it could be a good compromise.

  • Most banks here in Europe require Mobile apps to login into their website.

    • As far as I have evidence, that is not true in Germany. I have accounts with three banks, and all of them can be managed with SMS 2FA and web access.

      3 replies →

    • If you bank requires it, you can: a) find different bank that doesn't; there are banks like this b) demand a hardware token

      Unless you explicitly sign for Mobile-only bank (neobanks are weird) you will be able to get hardware token.

      Speaking from German, UK and Polish experience.

      2 replies →

  • If you want to go in and do the basics (check balance, do a normal transfer, look at activity) this can get you by. A lot of the more useful features tend to be app only though. E.g. "scan to deposit check" is an app only item for my bank.

    • I can do that sort of thing from the Ally website. Which is good, because Google is actively killing off support for devices more than a few years old, and I can't run most new apps on my phone, banking or otherwise (old apps are hit-or-miss, but the practice of forcing updates to the latest version poisons most of them).

    • You got a cheque? How quaint. I haven't used one in almost 2 decades. (Australia) in fact when telstra refunded me $2.50 by cheque I simply threw it away.

      This has to be a predominantly American problem, right?

      I cannot imagine a cohort of Australian, Asian, New Zealand, British and European continental users noping out of an app because not cheque enabled.

      1 reply →

  • Here in Europe you cannot login to bank websites without the bank app on your phone for 2FA codes

    • That's simply not factually correct. You can use bank web sites entirely without a smartphone. Banks supply this option as there are really - surprise! - people without smart phones who still has money.

      My own bank does not even use 2FA. I log in using the officiel state sponsored digital ID (yes, without having a smartphone). This is in Denmark.

      (sorry about the new anon account, it's been so long since I posted I've forgotten my old account. Perhaps I should use a PW mgr...)

    • Where in Europe? Everywhere on the continent? Certainly not in Sweden where I live. The major banks here use 2FA but not mandated to a mobile app.

      2 replies →