Hacker News new | past | comments | ask | show | jobs | submit login

I like the direction that Flutter has taken, cross-platform without the baggage of being a web platform.

If you know JS and Java, Dart is very easy to learn. About a few hours' worth of tinkering and you'll be good.

I had an Android app [0] that I was trying to build with Kotlin in the evenings/weekends. I switched to Flutter, and was able to get something out of the door in less than the time I spent on Kotlin/Java.

I like the mix between Flutter and being able to call native APIs. The only thing I'm missing right now is good maps support. Google and Mapbox have some prototypes, but it's still too early to use them (for what I want to do).

https://play.google.com/store/apps/details?id=za.co.movingga...




> cross-platform without the baggage of being a web platform.

Simple ability to run in the browser, even not perfectly, would still add a lot of value though..


From Laws of spacecraft design -> 39. Any exploration program which "just happens" to include a new launch vehicle is, de facto, a launch vehicle program.

I suspect adding ability to run in browser imperfectly would just invite demands for Flutter to become a web dev framework entirely.


Good point, but that would still be welcomed, though I'd probably prefer it be a diffeent product (ala the opposite of react-native).

Flutter has shown that it's possible to build a truly native implementation from "web" tooling. I've shipped apps with Ionic and such before (but not React-Native yet), but despite how much care goes into the application, they've still never felt native, and Flutter bridges that gap perfectly.

If it somehow managed to also be able to deploy the same code to the web, perhaps using a different (or providable) CSS grid, I think it's as close to a holy grail as we'll manage.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: