3 ms·
You are right. This is part of what made me try Flutter for a new app over RN. While it isn't perfect (no tooling is), the initial user experience is pretty goo
by latchkey 7y ago
You are right. This is part of what made me try Flutter for a new app over RN. While it isn't perfect (no tooling is), the initial user experience is pretty good and the documentation is constantly updated as the product matures.
- paulintrognon 7y agoI understand they are using the Dart langugage? Was it hard to master?
- latchkey 7y agoSuper easy if you know JS/TS and turns out that I actually quite like it.
- virtualwhys 7y agoWhat's missing? TS has quite a few interesting language features that I assume Dart is missing (seems Dart has the reputation of being a Java-like language, with all the boilerplate that that entails).
- latchkey 7y agoProbably my largest complaint is the need to use codegen for the json stuff. Sure you can type it all out by hand, but the codegen really does automate a lot of it for you. I have intentionally kept my very specific use case mobile app very very simple and not gone deep on the magic edge cases. It is a private app and will never be on the store. It is basically used as a QR code scanner to track equipment. I'm sure that if you have a lot deeper/larger apps you'd find more to complain about, but so far I'm happy enough with going from zero to full fledged app in about a month of work. IMHO, the boilerplate argument with Java is kind of outdated (Project Lombok and modern java solve a lot of that).
- bsaul 7y agoI used to be into flutter (theorically), but after seeing some bugs and performance issues, i’m now thinking the best combination would be : - write once and compile all business logic (and server and fs i/o ideally) into a portable independant libray, either in something that compiles to C, or wasm (once it’s more mature) - write native UI code using native tooling, and call the business logic library from there. But i haven’t settled yet on the ideal PL to write that library and have it interface easily on both android and ios.
- rabenblut 7y agoThis is the approach used with Kotlin multiplatform development. I suspect it will be the best way going forward, other approaches all have serious issues. https://kotlinlang.org/docs/reference/multiplatform.html https://kotlinlang.org/docs/reference/multiplatform.html
- izacus 7y agoThis is the approach we took at my current and previous mobile projects and has proven to be very effective (we chose C++ due to toolchain maturity over all platforms): - It forces you to think about your business logic vs. UI structure. - It forces you to make your core logic library easily testable. - Since you can deploy the core logic library anywhere, you get native, no Electron bullshit, support for pretty much all major operating systems at a cost of running a CI on all compilers to catch non-portable parts of C++ quickly. - The users get UI that's built for their platform with it's own quirks and doesn't burn 500MB of RAM. - Using a serializable and portable message standard (we opted for Protobufs) to communicate between logic library and UI part makes deployment to server easy as well. Biggest issues? - Getting inflexible people to learn anything other than JavaScript. - Getting slow compile times under control. - Getting CI coverage to the point where it catches developers accidentally adding Apple or Linux specific headers into codebase. - Learning to be conservative enough to not trust the platform and ship our own libraries. Even basic ones like SQLite.
- alien1993 7y agoHow do you achieve this? Are you using some framework like Qt? Or is it custom?