Live data from Hacker News

PinePhone Pro Announced

pine64.org

371–375 of 375 posts

Re: PinePhone Pro Announced

#371
post #270

Earlier quoted context omitted.

TBH I think having a flutter port for this operating mobile system is probably the most likely way for it to succeed. That way you can do a flutter app and it will work on this too, while still having mainline OS support. Then you would need to fill in some common services like push and such.

The most likely way to succeed would be to jump on the PWA bandwagon, IMO.

I think both would be necessary.

Re: PinePhone Pro Announced

#372
post #270

Earlier quoted context omitted.

TBH I think having a flutter port for this operating mobile system is probably the most likely way for it to succeed. That way you can do a flutter app and it will work on this too, while still having mainline OS support. Then you would need to fill in some common services like push and such.

Or run an Android or iOS emulator. (Note: like Wine runs Windows software on Linux in a fully legal way).

I think that is actually counter productive, since the emulated apps will always be shittier than their native counterparts, and you need to constantly deal with telemetry shims for Apple & Google lest the apps wont work properly.

Re: PinePhone Pro Announced

#373

Earlier quoted context omitted.

Theoretically you can run those apps via anbox. I've tested whatsapp via anbox on my desktop ubuntu install at least, and it works fine. Remains to be seen how well it'll work on this upgraded hardware, and I'm sure they're being conservative because of that.

There's also this somewhat new project called waydroid that runs android applications closer to the metal than an emulator would. https://waydro.id/

waydroid is an anbox fork afaik

Re: PinePhone Pro Announced

#374

Earlier quoted context omitted.

Because your pentium 3 GUI linux had a GUI designed around pentium 3 era hardware. All the linux phone GUIs seem to be designed around the latest in special GUI effects and animations and transparency. For some reason all the people who know how to design UIs for linux are incapable of understanding hardware requirements.

Check out sxmo.org if you're going for a minimalist UI. But the big feature that's missing on these old-style UI's (while it is in, e.g. Phosh) is smooth animations w/ direct 1-to-1 feedback, which is critical for usability w/ modern capacitive touchscreens and quite hard to achieve without GPU acceleration.

I've used a N900 and I don't see what massive difference there is between its resistive touchscreen and a capacitive touchscreen when it comes to user experience. The N900 achieved good feedback using the vibration motor and extremely basic animations. I don't think you realistically need more than what the Hildon UI gave you when it comes to a good user experience. The Hildon UI targeted much older hardware (albeit with proprietary graphics drivers). It should be possible to replicate the performance of the Hildon UI with the lima drivers if an explicit focus was placed on ensuring that above-all the UI was responsive rather than being pretty.

Re: PinePhone Pro Announced

#375

Earlier quoted context omitted.

>As a result, I cannot take any risks when purchasing a phone. Or you could make better choices when it comes to how you organise your life so that you do not get in situations where losing your phone completely screws you over. Seriously I don't get why people wilfully get into situations where important things in their life rest on the reliability of their phone. It takes a minimal amount of awareness. And there's…

The problem is what do you do about 2fa which more and more organizations are requiring almost always via sms ? I suppose yubikeys could be part of the solution of getting away from the phone for auth.

I don't see an issue with SMS 2FA. You can just move the sim card if your phone breaks and also it works without special smartphones. That being said I don't really see SMS 2FA in use that often (I live and work in the UK).

I've also not seen a massive push for 2FA which requires a special mobile-only application from organizations. Aside from my bank, where I have the option of a mobile app or a small calculator-looking token (I obviously picked the token), most 2FA I see is basic TOTP (which you can back up and treat as you like) or some third party solution which provides non-mobile options (and half the time someone has reverse engineered the software and there's an open source solution or it's actually just generic TOTP which you can run anywhere).

My work relies on a VPN connection and the the token is generated in a special mobile app, they have given me a smarphone for this purpose. I was informed by coworkers that if you reset the token and re-generate the key you can load the key into a slightly modified version of any TOTP program which uses a slightly different interval and it would work. But at the end of the day if my job requires this token and they give me a phone for it and that's the only source of the token and the phone breaks, I'm not going to really fret about it. It's not my problem to solve, all I have to do is contact my employer and get them to sort out getting me a new phone and getting me back up and running. Keeping this backed up is not my responsibility.

Post reply on HN