What It Was Like to Write a Full-Blown Flutter App

Flutter is good, I echo the author&#x27;s sentiments. I wrote a Flutter app for Android in a very short period, relative to my Android Java attempt.<p>The use of widgets saves a lot of time, leaving one to focus on connecting everything together. It&#x27;s also easier to learn than React Native (for me at least).<p>The current downside for me has been the lack of maps (I&#x27;m aware of current efforts). I also hit a weird Firebase Messaging bug that leads to an infinite loop of the app opening itself [0].<p>I agree with the author regarding the strong Firebase push. The community doesn&#x27;t yet seem large enough, so outside of wine of the Google supported plugins, it&#x27;s sometimes a struggle.<p>I am building a second app in Flutter, using the new Material stuff that Google announced this year.<p>[0] <a href="https:&#x2F;&#x2F;github.com&#x2F;flutter&#x2F;flutter&#x2F;issues&#x2F;18524" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;flutter&#x2F;flutter&#x2F;issues&#x2F;18524</a>

I really want to get into mobile development, but I have major obstacles with default platform APIs: I don&#x27;t have a Mac (and cannot afford one ATM), the Android Studio is unusably heavy for my decent laptop, and writing Android apps w&#x2F;o the studio seems prohibitively difficult. In this situation, Flutter is a liberating force for me. I have recently started learning it, and I can just keep writing my code in Emacs, while running the app on a phone with hot reload, and without my laptop melting. Thanks to whomever created it.

Can someone compare their experience with Flutter or even React Native, versus writing separate platform-native Swift&#x2F;Java versions for iOS and Android?<p>I don&#x27;t often hear about the true accounting of time spent learning and grappling with the limitations of cross-platform frameworks, including debugging and workarounds, versus just using the platform vendor tools.<p>It just sort of seems like it&#x27;s assumed that it&#x27;s a huge time waste to maintain separate codebases. But I wonder if you gain other advantages that might outweigh it, like not having to &quot;fight&quot; the intermediary layer and getting first-class access to the underlying APIs, platform features and debugging tools. Thoughts?

I totally understand the upside of writing one app for both platforms, but at the end of the day they are still two different platforms. It seems unlikely you’re going to make a high quality app unless you give each version the individualized attention they really need.<p>Maybe these dual platform frameworks are fine for something like a company internal app where it’s okay if you don’t get everything “just right”. But otherwise I’d rather just go pure native, even if it means alienating half my user base or spending 2x resources. It’s worth it in most cases IMO.<p>Granted I’ve only spent a couple weeks with React Native about a year ago, so maybe I just need to give it another go.

Flutter looks interesting. As a React&#x2F;React Native dev, I found this doc page particularly useful and enlightening:<p><a href="https:&#x2F;&#x2F;flutter.io&#x2F;flutter-for-react-native&#x2F;" rel="nofollow">https:&#x2F;&#x2F;flutter.io&#x2F;flutter-for-react-native&#x2F;</a>

I&#x27;m wanting to try Flutter for a new app I&#x27;m planning. But a blocker is that it doesn&#x27;t (yet?) run on Linux, which is a deal breaker for me.

I didn&#x27;t know what Flutter was and from the title I assumed it was abandoned (how it <i>was</i> to write a flutter app).<p>So, I just got that excitement from having something cool to learn.

The article mentions removing simple elements, e.g. &quot;‘Center’ widget is nice for a Hello, World container but I never understood it. Why can’t ‘Container’, something that’s way more prevalent have a property to do the same thing?&quot;<p>I&#x27;m perfectly happy with the nesting of simple elements. Having a single &#x27;Container&#x27; also handle various layout rules is what makes all the positioning options of CSS difficult. Similarly for constraint systems. Composable, single function components are easy to learn and use. I&#x27;m just presuming that it has good runtime characteristics and haven&#x27;t run into any issues yet.

Interesting this is on the front page, yet no comments. I&#x27;m very curious as to others thoughts. We are about to start a new react native app and are considering flutter. It will be webrtc based also. Extensive experienced design team, but no dart experience. Any thoughts?

I am working on an Flutter android app, I find it still very laggy. Even the official Gallery app from flutter team laggy. I am hoping they will sort it out by the time they release it from beta.

there&#x27;s a lot of enthusiasm, yet, i feel less enthusiastic about Flutter after reading this.<p>i had not thought about this right in the past. i hadn&#x27;t factored in the reality of needing to maintain two separate UI trees, one with Material Design widgets and one with Cupertino widgets. this makes me think one of the really big advantages i thought Flutter had -- a unified UI -- is not really realistic.<p>i must be misunderstanding this