Pinephone app development

[stamat]

@lupyuen used flutter for the Android and iOS versions of a PineTime companion app, but stuck to go for the linux phone version. Reasons are briefly mentioned in the article about it:
https://lupyuen.github.io/pinetime-rust-...icles/bloc
Things may have moved on since then though. It's not something I've tried so can't give any 1st hand info.

Thank you for the information @wibble. Some great work from lupyuen; information I will make use of for sure. I've been reading a little more and I'm convinced that Flutter is a great choice for developing things for the pinephone for many reasons. The only thing I can see biting you in the bum is incompatibly issues. I really like the idea of one codebase for several platforms. 

I've not done much with GO either TBH. I hear it's an easy language to pick up like dart and I was considering it for another web project of mine but never got around to making a start and now I'm looking at using Flutter for that too maybe.

I'm a systems administrator by day and don't do much programming day to day other than a bit of Python and the odd project in other languages when required so I need something simple to pick up and run with. Both GO and Flutter look like great choices for a guy like myself.

Hopefully I'll have something to share in a month or so.



->drgr33n, you opened a nice thread, but I would like to share another point of view with you and the thread readers: first, I would like to ask you, how do you think, what is the demand for this device (pinephone), I am not sure about the whole world, but I will tell you my demand, and I am strong in my intention, I will be short and will use simple words - Google have more light corporative policies for Android app developers compared to Apple iOS (and macOS too) app developers, the Apple corporative policies are disruptive (the MS corporative policies are even worse); but the technologies used by Google ... haha ... are not developer technologies, they are not even user/customer technologies, simply because they are not really system and native (down to the metal) technologies (OSes are writen in the system C or C++, and also there are other native technologies, which are and cross-platform too (like Qt, Lazarus,...)), Java and Kotlin, etc are mainly virtual techs, they could be nativerized (by VMKits, JITs, etc. staff), but they continue to use Garbage Collector even when they are "nativerized" (C++ uses smart pointers for really automatic memory management..., it is not the only reason to do not use virtual techs, actually, day by day they eat your hardware (with all the updates and new apps installed), and initially powerful and productive it goes slower and not enough, but Android devices are more low cost..., compared to Apple technologies and devices, Apple use system and native technologies in their place (Clang family, Swift..., in the Apple Development Agreement there is a sentence saying "in the store are not allowed deprecated technologies (like Java)"), because of those native technologies day by day the Apple devices are powerful and productive, but they are expensive and their accessories too. I am not against any technology, neither Java, neither Kotlin, neither Javascript (the new hardware eater), but they have to be used in their place and their place is not in the embedded systems! Of course you can use every thing you want in every place you want..., but why in this cases you do not use and develop under Android and iOS?! :-) - this was the second, and after that I am continue with the first, I would like this device to be all, which is not Android and iOS, to can run every pure Linux and Linux app and FreeBSD and app.
Good Luck to everyone! ;-)