Was flutter considered a candidate for the technical solution.
Too high risk of it being cancelled soon
Building a Cross-Platform Web and Mobile App from the Ground Up
21–30 of 32 posts
Re: Building a Cross-Platform Web and Mobile App from the Ground Up
#22Re: Building a Cross-Platform Web and Mobile App from the Ground Up
#23For those who have the pleasure and luxury to go green field new dev, i started using the Quasar Framework, which builds on top of Vue. I really love it. https://quasar.dev/
For those unfamiliar:
> Quasar’s motto is: write code once and simultaneously deploy it as a website, a Mobile App and/or an Electron App. Yes, one codebase for all of them (...)
source: https://quasar.dev/introduction-to-quasar#what-is-quasar
Re: Building a Cross-Platform Web and Mobile App from the Ground Up
#24How is this “from the ground up”? It basically uses the same web technologies and back end from the existing web solutions. Also, I missed the challenges of handling offline usage which was stated as a requirement, but the back end appears to be GraphQL queries to a server?
I guess it's "from the ground up" as in "greenfield", where there's no preexisting code to support or rewrite. I.e. "ground" means "fresh project" (and not e.g. entering bits by hand).
Re: Building a Cross-Platform Web and Mobile App from the Ground Up
#25Earlier quoted context omitted.
Too high risk of it being cancelled soon
What risk is that exactly? Dart and Flutter are one of the fastest growing languages and frameworks around.
Re: Building a Cross-Platform Web and Mobile App from the Ground Up
#26Was flutter considered a candidate for the technical solution.
We considered Flutter, React Native, Kotlin Multiplatform Mobile and pure native as solutions. The factors we looked at were size of hiring market, ease of conversion of web codebase and the effectiveness of the current team in that framework.
Re: Building a Cross-Platform Web and Mobile App from the Ground Up
#27How is this “from the ground up”? It basically uses the same web technologies and back end from the existing web solutions. Also, I missed the challenges of handling offline usage which was stated as a requirement, but the back end appears to be GraphQL queries to a server?
Yeah, I saw the headline and was hoping it was something crazy like Rust compiled for mobile and wasm
Re: Building a Cross-Platform Web and Mobile App from the Ground Up
#28Loved this
Re: Building a Cross-Platform Web and Mobile App from the Ground Up
#29Earlier quoted context omitted.
What risk is that exactly? Dart and Flutter are one of the fastest growing languages and frameworks around.
https://killedbygoogle.com/
This is one of the most pathetic answers possible. You give nothing on user bases and adoption of both dart and flutter, internal adoption within google, it's use of Dart and Flutter for the frontend of Fuschia, googles desire to control a widespread language, the open-source nature of Flutter, the list goes on. You just provide a list of PRODUCT's that have been killed off, not an entire language and frameworks. Your idea that google will just kill it off is a meme, and doesn't take into account it's usefulness to google in the wider world.
Re: Building a Cross-Platform Web and Mobile App from the Ground Up
#30Earlier quoted context omitted.
https://killedbygoogle.com/
This is one of the most pathetic answers possible. You give nothing on user bases and adoption of both dart and flutter, internal adoption within google, it's use of Dart and Flutter for the frontend of Fuschia, googles desire to control a widespread language, the open-source nature of Flutter, the list goes on. You just provide a list of PRODUCT's that have been killed off, not an entire language and frameworks. You…
Firstly, chill out :-)
In terms of user bases, Orkut (RIP) had north of 60 million users when Google killed it. It was the primary social network in multiple countries.
Maybe the biggest user base killed off was Google Reader (RIP), it was the world's foremost RSS aggregator with no forseable competition and no obvious exact replacement for all those users to go to when GReader was turned off.
In terms of languages and frameworks, the Noop language was killed more by Kotlin than by Google but Google App Engine has been crushed even if the name lives on, the old SDKs you relied on are mostly gone. There all alternatives, but not quite as attractive.
Lastly though, that page i linked has a LOT of examples on it. I feel that adds weight.
Hopefully this longer comment goes some way to assuage the idea that my prior comment was a thoughtless throwaway.
All the best,