roszkowski.dev
Flutter Developer, GDE, building Visible - tracking platform for chronic illness
#flutterdev
132 posts
294 followers
93 following
Regular Contributor
Active Commenter
comment in response to
post
Looking forward to see scrolling and gestures snappier thanks to platform thread merging.
comment in response to
post
With some back and forth testing using internal app sharing on Google Play you can just use Google Play SDK APIs directly from Dart
comment in response to
post
It would help if LLMs would have a bit of scepticism included. I'm anthropomorphizing it a bit, but in my human terms I'd prefer my LLM model to say "there's not enough data to answer" than spitting fairly probable garbage that I need to sieve through :)
comment in response to
post
When writing I often delete entire sentences, when speaking I correct myself etc. When thinking about code I see parallel "topics" at the same time.
The success of LLMs shows how predictable majority of the work we do is, though.
comment in response to
post
I had this feeling when the Chat GPT et al. launched some time ago - in reality this is what we do whenever we speak or write down our thoughts. You don't really know what's going to be the next word until you say it :D
But on the other hand we also realize that it's not only about it.
comment in response to
post
Canonical says they "are hard at work expanding this availability, and we will soon release multi-window support to both Linux and MacOS-based platforms."
ubuntu.com/blog/multipl...
#Flutter
comment in response to
post
Haha, yes, I prefer all in one apps that have at least all of my calendars and email accounts and can deal with snoozing, scheduling etc. Ideally it's native and offline first too.
comment in response to
post
The new one (paird) that can be downloaded from the website is Electron based. The one in AppStore (Spark 2) is native.
comment in response to
post
Yup I'm using the classic (non-electron) Spark. It does the job very well
comment in response to
post
Urgent and important first, then important, and make sure to do something just for yourself every now and then :)
comment in response to
post
Splendid repro steps!
comment in response to
post
Some real data before (Flutter 3.24.4) and after (3.27.1 + pub workspace)
AAB size before: 142 MB
AAB size after: 141 MB (including Firebase update)
IPA size before: 68 MB
IPA size after: 55 MB
Imho the size change may be related to some of the transitive dependencies getting updated
comment in response to
post
I got some perf improvement in my vs code as there's only one dart analyzer context instead of 30+
comment in response to
post
Don't like the platform and their patterns that much as well, but it's just one I chose some time ago. Before that I would use Twitter's revue but it's long gone now.
comment in response to
post
Substack has better discoverability, similar to medium or dev.to. Being able to "push" blog note to hundreds of readers is way more effective than posting link to the website. I keep it on my site for redundancy and posterity ;)
comment in response to
post
I will try to build intent receiver and will check!
comment in response to
post
I've also posted this on my website for those who prefer classic blogs and RSS feeds roszkowski.dev/2025/native-...
comment in response to
post
Future looks exiting, but in this area Flutter seems to be lagging behind KMM/Compose Multiplatform.
comment in response to
post
I'm looking forward to some of the official plugins to migrate from pigeon and method channels to direct native interop. Next step seems to be to officially expose some of the platform APIs so that you won't have to do it yourself, but rather consume a dedicated package e.g. package:ios
comment in response to
post
What is quite important to note is that:
- this is not new in cross platform (Xamarin and KMM both have it)
- this has been possible with ffi and jni but finally it's approachable to normal developers
- the work on swiftgen is not that advanced just yet
comment in response to
post
It would probably work better to call it "entered stable mode/release cycle" or something along these lines.
comment in response to
post
I put washing machine salt instead of dishwasher salt once. After few weeks the entire softener module that keeps special resin got clogged. Fortunately I found a person who fixed it within few hours.
Since then I'm always checking the label before putting something into dishwasher/washing machine.
comment in response to
post
Sorry for keeping you busy on bluesky with debugging my requests :D
Interestingly the long requests sub-steps are not that long, and some of them don't really show anything detailed.
comment in response to
post
Is this what you refer to? I just had to wait 2 minutes for the references to a widget to be found :(
comment in response to
post
Over 4 thousands files modified, love it
comment in response to
post
7) Do they use server-driven dynamic layouts? If yes, what strategy do they use - e.g. some custom representation of layout driven by CMS, or maybe remote flutter widgets, or maybe plain HTML in a webview?
#AskFlutter
comment in response to
post
6) How do they do logging and remote troubleshooting? Do they collect logs from every user or just selectively? Do they have ways to enable tracing or debug-level logging remotely? If yes, what kind of tools do they use?
#AskFlutter
comment in response to
post
5) When working in multiple regions how do they handle various legal requirements that can differ across jurisdictions? At which point the app knows in what country it's operating and exposes features. Is it account-based, or maybe known at startup of the app?
#AskFlutter
comment in response to
post
4) How quickly do they adapt the latest stable Flutter version? Have they migrated to Impeller?
#AskFlutter
comment in response to
post
3) Are their apps offline-first or at least offline-capable? What strategies do they use to synchronize the data, maintain schema migrations, queue actions and expose failures to the users?
#AskFlutter
comment in response to
post
2) How do they maintain contracts between mobile app and backend? Do they use API versioning, contract generation, grpc, protobuf?
#AskFlutter
comment in response to
post
1) Have they found good ways of automated testing with native features (BLE, camera, payments, deep links) eg using maestro, browserstack etc? Or just go with manual QA?
#AskFlutter
comment in response to
post
Damn, I forgot #AskFlutter
comment in response to
post
7) Do they use server-driven dynamic layouts? If yes, what strategy do they use - e.g. some custom representation of layout driven by CMS, or maybe remote flutter widgets, or maybe plain HTML in a webview?
comment in response to
post
6) How do they do logging and remote troubleshooting? Do they collect logs from every user or just selectively? Do they have ways to enable tracing or debug-level logging remotely? If yes, what kind of tools do they use?
comment in response to
post
5) When working in multiple regions how do they handle various legal requirements that can differ across jurisdictions? At which point the app knows in what country it's operating and exposes features. Is it account-based, or maybe known at startup of the app?
comment in response to
post
3) Are their apps offline-first or at least offline-capable? What strategies do they use to synchronize the data, maintain schema migrations, queue actions and expose failures to the users?
4) How quickly do they adapt the latest stable Flutter version? Have they migrated to Impeller?
comment in response to
post
1) Have they found good ways of automated testing with native features (BLE, camera, payments, deep links) eg using maestro, browserstack etc? Or just go with manual QA?
2) How do they maintain contracts between mobile app and backend? Do they use API versioning, contract generation, grpc, protobuf?