Luke Greenwood 💙

A little insight into what I’ve been working on lately with @FlutterDev and @rive_app with a bit of help from Firebase AI ✨

People saying Flutter is dead because AI makes it easier to make native apps are missing that AI also makes it easier to make Flutter better 😂

@chebibu @FlutterDev @rive_app 🏃🏻‍♂️

@_luketg8 @FlutterDev @rive_app dont wait for the weather my bro, just go and kick the shit out of your sneakers

A little insight into what I’ve been working on lately with @FlutterDev and @rive_app with a bit of help from Firebase AI ✨

Also available for Android - play.google.com/store/apps/det…

Check out the Kozy app - apps.apple.com/app/kozy-anxie…

@luke_pighetti Gone all in on Rive with this one - apps.apple.com/gb/app/kozy-an…

what’s everyone building right now?

R I V E

I had a bit of a headache today so, instead of being productive, I wrote a rant. Here it is: filiph.net/text/ai-is-a-p…

@SuprDeclarative @damy_wise Been going great for our Flutter + Rive app, View Models have been a game changer for us apps.apple.com/gb/app/kozy-an…

@damy_wise I’m about to move my focus from Flutter to Rive. Curious to hear your thoughts based on your experiences.

Flutter-Native/Webview-Flutter migration|Part 2 Initially I was experimenting around, trying to find ways to improve performance. I don't know why but I tried to migrate the whole settings window into Rive, which now I know is stupid; now that I'm older and wiser.

Another month, another blogpost! filiph.net/text/i-don't-t…

@luke_pighetti FINALLY

@chimon1984 Yet to really try it out, how is the mutation syntax feeling? I know there was a lot of back and forth on that

Been playing around with Riverpod v3. It's great.

@luke_pighetti @rive_app @WillTesteil

please tag all the best @rive_app contractors

@caseycrogers I’ve used them a lot too, both in Flutter and React and I abandoned them on Flutter after having to onboard some devs to use them. They just feel too alien in a Flutter codebase and are so easy to mess up with

@_luketg8 I use hooks on a day to day basis and I agree the magic is really bad, but IMO more around how an ostensibly stateless thing (a pure function call) is secretly stateful through complex subtle machinery. I think there’s a lot of ROM for things inbetween.

I really don't like the service pattern seen in a lot of #Flutter code. Its adds unnecessary indirection. People say it helps testing, but I find faking the HTTP client itself to be a much more effective testing strategy-and it doesn't pollute your production code.

@caseycrogers I completely agree, I have done similar with both builders and mixins!

Agreed that your async button flow needs to be independent from your form system, but also easily composable with your form state. Separate, but very easy to wire together. I had an inherited widget based system where it holds the action and the state at the top of the page and the button binds to it and anything else that needs to display state can reference it.

@caseycrogers Also async handling goes beyond just forms too. Internally standardising (as much as possible) loading, success + error states and just overall async flow in general is a must

@caseycrogers I'd also argue StatefulWidgets aren't tedious for init/disposal compared to the extra complexity of another abstraction layer, I actually have grown to quite like the in your face explicit lifecycles compared to something like hooks

@caseycrogers I'm all for abstracting the logic into functions/classes outside the widget, just not the part that directly interacts with the form or other ephemeral state. Flutter already handles that well within widgets - adding extra controllers just adds unnecessary boilerplate

@caseycrogers imo a form controller here creates unnecessary indirection when Flutter already has built in support for forms and local state, so you're just fighting the framework 👇