The most important question missing from the FAQ is whether bank apps, government ID apps, etc. will work with this phone.

▲

crote 10 hours ago | parent | next [-]

Everything hinges on app support.

Smartphone apps have unfortunately become a hard requirement for basic day-to-day activities. Most companies offer them only for iOS and Android.

If your smartphone can't run the vast majority of apps, it is basically dead on arrival. Nobody is going to buy it when they need to carry another phone anyways.

The only way around this is either emulation (which Google is trying very hard to sabotage) or heavy-handed regulation forcing app developers to also support niche platforms. I don't think either option is likely to work.

▲

sgerenser 9 hours ago | parent | next [-]

They don’t need to specifically support “niche platforms,” which will never happen anyway. They just need to support the one, universal platform every device (be it phone, laptop or desktop) can always access, the web.

▲

pbmonster 9 hours ago | parent [-]

And they don't want to, because that experiment ran for around 20 years and resoundingly failed. Turns out it's really hard to stop the bottom quintile of users from entering all their credentials into just about any website that looks similar to what they are used to - and then their identity/money is just gone.

Stopping those users without a trusted authority deciding which electron-wrapped websites are genuine is an unsolved problem, I think.

▲

Normal_gaussian 6 hours ago | parent [-]

If the app truly just plumbed a webview and cert verification - which has been doable for over a decade - it would be very portable and this wouldn't be a problem.

The apps don't just do that though; they call into and use an awful lot of the system APIs for user tracking / semi-native experience / biometrics and probably a whole host of other things. Its the incompatibility in these that drags compatibility.

	▲	pbmonster 6 hours ago \| parent [-]
		> The apps don't just do that though; they call into and use an awful lot of the system APIs for user tracking / semi-native experience / biometrics and probably a whole host of other things. Its the incompatibility in these that drags compatibility. Both can be true. Many (most?) online banking apps are just shitty wrapped javascript, that also uses an awful lot of system APIs. I'm using a couple of different banks, and not a single one has anything close to a native app. Because how nice would that be? Responsive interface (since it doesn't need to load every single view from the server), instant search over your transactions (since the DB can be cached locally), instant access to all the PDFs in your inbox... but no.

▲

bryanrasmussen 9 hours ago | parent | prev | next [-]

>heavy-handed regulation forcing app developers to also support niche platforms.

should work for banking and governmental applications, especially as those should already have the workflow in place to support niche platforms.

▲

kleiba 5 hours ago | parent | prev | next [-]

> Smartphone apps have unfortunately become a hard requirement for basic day-to-day activities.

I've never owned a smartphone in my life and are not planning on getting one, and I'm going through life just fine.

	▲	postdoc74 2 hours ago \| parent [-]
		Maybe you don't live in any European country. 2FA with cell phone has become compulsory for most banking procedures in Spain, to the point that I can even no longer assist my parents without being present there with them. Even when there is a web app, this randomly forces the user to confirm identity via phone. Every day this extends to more and more official proceduress these days (e.g. loging to EU pages, regional government paperwork, access to hospital records and prescriptions...), and unfortunately it seems to me that the phone as official ID might be the future. In this scenario, projects like this one cannot be really useful without some standardization or layer that makes it acceptable by the government.

▲

Zigurd 5 hours ago | parent | prev [-]

Although I haven't held one in my hands, apparently there's Flutter support for Harmony OS. There are quite a lot of mobile apps implemented in Flutter and Dart, and platform support for alternative phone OSs looks doable.

▲

mpol 10 hours ago | parent | prev | next [-]

There is a Wiki maintained by users. In short, it depends :)

https://sailfishos.wiki/books/compatibility-list-of-android-...

	▲	Taro3 10 hours ago \| parent [-]
		[dead]

▲

rekabis 16 minutes ago | parent | prev | next [-]

The need to support apps - when you are constantly internet-connected anyhow - is becoming less and less important. You can now pin many websites to your phone’s “desktop” and have them run identically to native apps, and sometimes with even better start-up performance.

So long as a service is being provided identically on a mobile website as it is in a native app, you can pin that website and get just the same experience without needing a native app.

▲

carlosjobim 4 hours ago | parent | prev [-]

It's not a huge hassle to keep another phone around for these things, if you really want to have a Jolla phone.

Of course they cannot answer this in the FAQ, because they have no insight into how thousands of different banks and other third parties will make their decisions on which devices to allow.