Latency has been the main UX concern we've heard for @FlutterDev teams building GenUI/A2UI experiences. The new Jev model from @typesafeai solves this and unlocks a ton of new potential.
All the UI generated in this video was picked by Jev - it felt like everything was running locally!
Flutter had zero iPhone Duo support. Now it has a package. 🥳
foldable: hinge angle, fold posture, crease geometry and size classes, straight from iOS 27.1 to Dart. Safe on every non-foldable device too.
https://t.co/zD2R8ddYoG
#Flutter#iPhoneDuo#FlutterDev
@volklub@YokohamaIndia what should i choose for my Xuv 3xo,
also if we replace should we replace pair or fine with just one ?
one of tyre got several punctures more than 8,
so looking to replace it,
@volklub Have 3xo,
Recently got punctured ans and didn’t notice during driving
Got run little and crushed it
Had to do 7-8 punctures
Any suggestions for new tyres to consider
Had run around 15k
📣 Starting with the next stable Flutter release, 3.44, Swift Package Manager replaces CocoaPods as the default dependency manager for iOS and macOS apps → https://t.co/lbC5aWt9uG
This means no more messing around with Ruby or CocoaPods installations to get your app running!
Unpopular Opinion: We aren't building the future 10x faster with AI. We are just generating legacy code 10x faster.
Everyone is currently bragging about developer velocity. "I built this entire backend in a weekend!" "AI wrote 80% of my codebase!"
But here is the reality check we are ignoring: Code is a liability, not an asset.
If an AI tool spits out 1,000 lines of functional boilerplate in five seconds, that is still 1,000 lines that a human being has to read, review, secure, and maintain when the dependencies inevitably break next year.
We are treating code generation like a pure productivity win, but we are optimizing for the wrong metric. The bottleneck in software engineering was never how fast we could type. The bottleneck has always been comprehension, architecture, and maintenance.
If we don't shift our focus from "generation speed" to "architectural sanity," the tech debt of the next five years is going to be an absolute, unmaintainable nightmare.
Is there a good tool on the market (or workflow) to build mobile e2e tests? Maestro is good for running but misses ability to discover flows in the app.
I would love something that can be scripted afterwards to support parametrization, conditionals, external API calls.
On Monday this year's Advent of Code starts,
and as usual we're having a Dart leaderboard! 🥳
If you are planning to do the puzzles in Dart, join the Dart leaderboard using this invite code:
425912-8e09f2ba