Live data from Hacker News

Flutter 3.47

flutter.dev

171–180 of 231 posts

Re: Flutter 3.47

#171

I vouch for Flutter over React Native; we built https://macrocodex.app/ with 16,000+ users already! And it's completely free no ads, no subscriptions, or donations, for the public benefit of improving health and fitness. It's a guaranteed weight loss or gain app; results within 2-5 weeks! Don't believe? well just read reviews. We do not have Revenue, so no money to spend on marketing. OK so that's brief description o…

I'll second this. I avoided React Native because I absolutely loathe using React in general (much prefer Vue/Nuxt or Svelte/SvelteKit). Flutter has been an absolute pleasure to build the mobile version of https://miserablyunemployed.com with. It's all really straightforward and I haven't experienced any real gotchas yet.

Re: Flutter 3.47

#172

I vouch for Flutter over React Native; we built https://macrocodex.app/ with 16,000+ users already! And it's completely free no ads, no subscriptions, or donations, for the public benefit of improving health and fitness. It's a guaranteed weight loss or gain app; results within 2-5 weeks! Don't believe? well just read reviews. We do not have Revenue, so no money to spend on marketing. OK so that's brief description o…

As someone coming from MacroFactor, estimating macros on food is the hardest part of dieting. So your app is great but it tackles the part of dieting that people aren't stuggling with and doesn't address the part that they do struggle with. Most dieting apps are pushing for the AI photo and barcode scanning to make estimating easier and though far from perfect, it makes the whole experience at least somewhat doable.

>As someone coming from MacroFactor,

We've had many people who have unsubscribed from MacroFactor after using our MacroCodex.

Not just this, we've also built MacroFactor Workout's rival Symbiote Workout app which is also completely free! it's now in Beta and under rapid developement.

For calorie tracking, you've established apps like Cronometer and MyFitnessPal or they can use our completely free AI calorie tracker CalorieCodex! which does what you want! barcode scan / photo to calorie and macro output etc...

>estimating macros on food is the hardest part of dieting. So your app is great but it tackles the part of dieting that people aren't stuggling with and doesn't address the part that they do struggle with.

I believe MacroCodex actually targets the part most people are likely to struggle with and this is why it is able to provide guaranteed results!

This app is not a calorie tracker, though it can pull calorie totals and weight from other apps using Health Connect on Android.

To understand the problem we are solving, you'll need to read this: https://macrocodex.app/knowledge/rethink/adaptive-tdee/

We've had to design this algorithm to figure out real maintenance calories:

https://macrocodex.app/knowledge/macrocodex/smart-calorie-bu...

>Most dieting apps are pushing for the AI photo and barcode scanning to make estimating easier and though far from perfect, it makes the whole experience at least somewhat doable.

We also have an AI calorie tracker; it's CalorieCodex. It's in BETA and can do Barcode/Photo using BYOK AI.

Re: Flutter 3.47

#174
post #81

I still prefer React Native with Expo over Flutter, mostly for practical reasons: * Language and hiring: TypeScript has a much larger developer pool. Dart is a solid language, but finding experienced Flutter engineers is harder. * Platform model: React Native maps much more naturally to native platform concepts. Flutter owns much more of the rendering stack, which is powerful, but also creates another abstraction lay…

As someone who used all these frameworks professionally for years, I highly agree. Although, I do not prefer Expo due to it's highly annoying build system and dependency hell, but React Native itself in that case. While I understand Google wants a horse in this race, Flutter doesn't feel like a horse to bet on. - Dart is a really _ugly_ language with lots of tiny annoyances. Its as if someone took worst parts of Java…

> Although, I do not prefer Expo due to it's highly annoying build system and dependency hell

Highly agree with this. I'm almost done moving an app off it into React (web, not native) because the SDK upgrades kept including unlisted breaking changes to the point I can't upgrade anymore. Biggest culprit was Reanimated.

Re: Flutter 3.47

#175

I vouch for Flutter over React Native; we built https://macrocodex.app/ with 16,000+ users already! And it's completely free no ads, no subscriptions, or donations, for the public benefit of improving health and fitness. It's a guaranteed weight loss or gain app; results within 2-5 weeks! Don't believe? well just read reviews. We do not have Revenue, so no money to spend on marketing. OK so that's brief description o…

I wanted to love flutter. It’s just so hard to commit to anything like this Google makes without a full expectation of getting rug pulled.

I think they are planning to offload it to an open-source foundation! I remember having received a questionnaire along those lines!

Re: Flutter 3.47

#176
post #160
post #135

Earlier quoted context omitted.

> it's unsolvable since you need to download the whole world (a few MBs) to have the app running on your browser another reason why the web should move from whole app bundling to content addressed CDNs for library code. you would only need to download one copy for each framework version not every site. and its easy to make it decentralized with IPFS if you want.

Shared caches stopped working years back, to close a security hole. They're redownloaded per domain now. https://dev.to/rstacruz/public-cdns-arent-useful-anymore-2b6...

There’s a proposal to bring back cross-site file caching with a fix for the privacy issue:

https://github.com/WICG/cross-origin-storage

Re: Flutter 3.47

#177
post #81

I still prefer React Native with Expo over Flutter, mostly for practical reasons: * Language and hiring: TypeScript has a much larger developer pool. Dart is a solid language, but finding experienced Flutter engineers is harder. * Platform model: React Native maps much more naturally to native platform concepts. Flutter owns much more of the rendering stack, which is powerful, but also creates another abstraction lay…

You should try Dart/Flutter again, they've improved a lot. - Dart. It's richer than JS/TS with stronger type safety, and seems purpose-built for UI. Fewer Dart developers than JS, but I'd argue those JS developers cannot be immediately effective coding React Native (Expo) anyway. - Emulated components vs. real native components. For multi-platform apps, this is actually desirable. These kinds of apps have their own d…

Is it now possible to use native font stack of OS? Last time I checked, it wasn’t possible and apps had to bundle custom fonts as workaround.

Re: Flutter 3.47

#178
post #168
post #164

Earlier quoted context omitted.

The internal divisions with this are really amusing. The big driver towards Flutter seems to be needing an iOS app, but Google really underinvests in those (YT being the exception, but it might as well be a different company).

If you want to have more fun on this matter, https://www.youtube.com/watch?v=VX6nAvRWQg4&t=3418s

Companies at the size of Google naturally have different business units with different goals. Flutter solves something from some teams with other parts of the company that do not solve for them. That doesn't mean there are some sort of systemic problems. It just means that it operates more like a series of smaller companies in many ways, which is overall healthier for everyone. It's confusing that everyone always expects some sort of unified strategy from the top. That's like suggesting countries should act more like dictatorships rather than democracies.

Re: Flutter 3.47

#179
post #154
post #128

Earlier quoted context omitted.

While the server side is still growing and obviously not as huge as Java etc., Dart definitely is being used on the backend. For instance, https://pub.dev/ itself is written in Dart: https://github.com/dart-lang/pub-dev . :) The language, like any other, does have some weaker parts, but in general is _very_ nice to write in - thanks to both the language itself and the toolchain built around it. The apps compile to na…

For production you may consider using dart VM also since it benefits from AOT and can actually be faster than a binary after it gets hot, similar to Java.

No, we (Dart team) recommend to deploy everything in AOT mode.

JIT mode is only for development, and its performance has not been a priority for a while now.

Re: Flutter 3.47

#180
post #127

Earlier quoted context omitted.

Why would you want apps on different os look exactly the same?

Why would you not? I use Ableton, Figma, and Emacs regularly. I have a decade (or more) of muscle memory around these apps. If they suddenly decided to adopt the look, feel, and conventions of their underlying host platform, I’d be very upset. If I’m using Emacs, I don’t want to use Cmd+S to save my files on macOS and Ctrl+S on Windows. I’ve already memorized C-x C-s. I don’t want Ableton to adopt whatever new design…

(Adding this as a comment because I'm over my edit window.)

I want to add a third category to the categories that make sense as native apps: apps that are built by the platform vendor (and potentially shipped with the platform).

GNOME apps are built with GTK+, KDE apps are built with Qt, and macOS apps are built with SwiftUI/AppKit. This is how it should be. Microsoft is the only outlier here, shipping apps built with everything from Win32 to React Native to Electron to their own WebView2.

Post reply on HN