I've added iOS style swipe gestures to a branch of our android app and now I want it everywhere. I still believe system back gesture is superior because of how ubiquitous it is, but I really enjoy having both options. I keep accidentally swiping on our production app to try and go back
"infinitely improving things with zero external impact"? It seems to me that external impact is how we define improvement. It might be second order impact of improving future work or surfacing bugs quicker, but there should eventually be an external impact. Otherwise it's pointless churn
I've found it often "digests" the design and then builds something similar. Maybe there's some lossy textual description in the middle. It builds the "same" thing but not the exact thing a lot of the time.
That's basically the experience for anyone with a W2 job right now at an "AI first" company. I've thought about token cost zero times and I get paid a salary to use them
Something I love about the android developer ecosystem is that things just get better for free over time
Nav3 for compose is so incredibly cool because what do you mean I can write my own scene strategy and get exactly the layout and transition behavior I want without the screens themselves even needing to change. Makes everything else I've ever used feel like handcuffs
The #1 thing that could make CMP easier to figure out would be to align coordinates for dependencies so I don't have to do the song and dance of figuring out what version of an androidx package corresponds to the jetbrains coordinate. Someday I want to add compose as a dep and start coding
Thanks for sharing this. I've noticed that my agent often has a "false start" where it will try a gradle command incorrectly (often running outside the directory) and then catches itself and tries again. Hopefully this helps skip that first attempt
Do I have to tell it to use sub agents or will it automatically do that to preserve the context window? When I use the codex app is seems to just do the right thing
Similar setup as the recent compose desktop hot reloading? Or is it a different route?
Messing around with the new desktop mode on my Pixel is surprisingly good! @heron.tunji.dev mostly handles things like a champ on my 5k monitor. A few more years of tweaking from Google and I could see this being a real daily-driver for people.
Are there docs anywhere for the "I want to add a gritql lint to my codebase for our own specific needs" use case? I tried a few months back and eventually gave up because I couldn't figure out how to get things off the ground (the playground will probably help a lot for next time)
I'll have to give it a try. Is there any sense of what should be better about the new solution over the plugin?
Spm import support sound great! We're currently using a 3rd party plugin for that right now. Since there's already a working plugin will that serve as a quick start for the new version?
Good read! Literally have a meeting in a few hours to talk about whether we want to rework our IAP setup (RC is one of the options being discussed I believe)
I noticed the heron bow right before I saw your update post! 10/10 super fun delightful animation that doesn't waste time
I'm super excited to try out the auto wiring and cleaner multiplatform support. expect-actual modules aren't the end of the world but it'll be nice to not have to do
Was just thinking how nice the app looks in the video! Just goes to show attention to detail and high quality craft are not a function of framework but rather mindset
Yep, clearing the app data gets things back into a good state 👍
I assume there will be a crashlytics/play console event to check but if you need any more information from me I'm happy to help
Crashes on launch for me after the update 😥
Built a ksp processor to generate jsi/ts glue code so that we can easily build kmp modules that bridge to react native on both iOS and Android with type safety and proper suspend/flow support. Still needs some work before we ship but that's no fun so that's "after holiday" work
Fwiw anyone on android who wants a smoother experience should check out @heron.tunji.dev (not involved, just a huge fan). Really highlights what a good native app can look like. Still early days so expect some rough edges but the bones are much better
When we first tried our migration and it went horribly wrong we investigated what experiences others had. It was helpful to see the bsky git history of trying and rolling back. We're going to try again soonish and hopefully things go smoother
Honestly the loading indicators (pretty much every variant) of expressive are the best parts! Somehow fun an dynamic without being over the top and annoying
Ah okay. The 25 toned things way down and looks a lot more like a traditional instrument cluster. I appreciate that they are willing to take big swings and then walk it back where appropriate
What year is this? I have an Ioniq 5 and I've never seen this before
I'm really interested in your use of buck2, is this the first thing you've used it on or have you been using it in anger for a while?
Isn't this basically java's checked exceptions? Also you should check out error types coming soon in kotlin, very similar idea but uses union return types instead of throwing (more akin to Result in Rust or multireturn values in go minus the problems)