@msfjarvis Ah that looks perfect. Thanks for pointing this out!

@msfjarvis that's actually how I figured out my information could get exposed, by one of them offering this service.

But I wasn't completely sure how they will mask it, and if they will use it themselves somehow.

And I just wanted to move along with the process, so I went with Github Pages for now.

I hope to revisit this properly at some other point in the future.

Publishing to MavenCentral has a learning curve to say the least 😅

I was about to buy a domain, then learnt that my information would be exposed on whois. Not too long after I learnt that Github Pages exist!

Now I'm messing with gradle configurations. Wish me luck 😄

#AndroidDev

Debugging sessions are much more enjoyable when they're performed like steady and calm science experiments rather than expecting fast results immediately then cursing in frustration because my programmer ego is hurt.

#AndroidDev #programming

Coding with AI teaches the discipline of going slower when we can go faster.

We still need to review the code, and we still own a 100% of it. We cannot review a 1000 lines of code in one go, but we can review them in small chunks at a time.

If we would like to maintain quality, then we need to slow down the process to a human level.

#generativeAI

This is my current iteration on recreating the iOS 26 navigation bar on Android. I hope to release this soon as my first open source project 🤞

#AndroidDev

The shared element transition API in Compose is quite powerful. It allowed me to achieve exactly the custom behavior I need.
And thanks to the documentation page below, I was able to understand how to resolve all the visual artifacts I was seeing.
https://developer.android.com/develop/ui/compose/animation/shared-elements/customize

#AndroidDev

Thanks @jetbrains for a greatly organized #KotlinConf, and thanks to all the speakers who shared their knowledge with us.

The biggest thing I'm excited about is Koog, the Kotlin framework for building Agents. I'm already getting my hands dirty with it.

#Kotlin

I created non-recomposing size modifiers to improve the regular ones that cause too many recompositions due to animations.

The code is shared in the gist below. Feel free to copy it :)

https://gist.github.com/elyesmansour/43160ae34f7acbec19441b5c1c6de3ab

#AndroidDev

@pberry thanks, I'll give it a shot!

@pberry @timbray oh this is interesting! I like to listen to podcasts on the way to work and back, and my reading list only keeps getting longer.
What tools are you using for this?

Auto-format a phone number in a text field.

Does the basic filtering and adds on top an implementation for visual transformations to make the user experience smoother.
https://developer.android.com/quick-guides/content/auto-format-phone-number?hl=en

Animate character-by-character the appearance of text.

Turns out emojis span over multiple characters, and there's a BreakIterator class that handles that.
https://developer.android.com/quick-guides/content/animate-text?hl=en

I came across these Android Quick Guides in the official documentation.
https://developer.android.com/quick-guides

They're supposed to be very practical and only take a handful of minutes to be used.

Found some interesting ones. I'll write them down in the thread 👇

Has anyone tried MotionLayout Compose? We're thinking of migrating our XML MotionLayout since our composables need to live in separate views as they animate separately.

Are you using JSON to define your scenes or are you defining them programmatically?

Our scene is pretty complex, and I'm concerned that JSON won't have autocomplete and references.

@androidweekly thank you for linking to my blog post! It was a nice surprise when a coworker let me know yesterday 😄

@kingargyle thanks for your reply. I generally agree with what you're saying. For my case in particular, I'm using it as an extra safety measure in a place where a crash is very unlikely and a second or third tap from the user may as well solve the issue.

But I still wanted this issue to be quite visible to my team while testing in case my doubts were well placed. It's a good enough approach for an unlikely issue 😁

@mez Thank you for your feedback. I truly appreciate other devs' POVs ❤️

I think this solution is good enough for now as I'm only using it to catch unlikely errors in navigation and not sure yet if it's worth investing time for a proper handling. The logs will help me evaluate that in the future.

@nikclayton good points Nik 👍

Currently I'm using this as a last resort for unexpected navigation errors that weren't property handled with an error state.

However I see we could also add another error state for this case like a simple toast. It might be less frustrating to the user than the app providing no feedback to their actions.

Thanks for your input 😊

@nikclayton curious to see why you think that. Could you please elaborate?