Prince Promise

@github_skydoves @GoogleDevExpert @AndroidDev Congratulations, buddy

I’m super excited and honored to announce that I am now an official @GoogleDevExpert for @AndroidDev! 🎉 Thank you to everyone who supported me on my amazing journey and I’m looking forward to contributing to the community more. 💙 I’m really glad to be a part of this!

@AndroidDev_News More inspirations 🎉

Dear #AndroidDev, 🎉 Happy New Year 🎉 I wish you all the best for 2026! * A year bug free * Short compile times * Exciting new technologies * Smooth updates * A healthy work/life balance Happy coding for 2026! 👨‍💻💪

@codewithimanshu @hayesdev_ absolutely 👍

@hayesdev_ That's a scary thought, Hayes, but I reckon upskilling is the only way to stay relevant in this changing world, you know?

@iyoushetwt Bracket 🙂

What was the first code editor you ever used? Mine was Sublime Text

@VasiliyZukanov @donnfelker I totally agree with you 😁

@donnfelker I actually suspect that AI will give the unsocial, but talented and motivated nerds a huge lift, because: 1. They won't need to communicate with as many people as they had to in the past. 2. AI is a great "soft skills" filter for written communication

The software engineers that have a solid foundation of soft skills are going to be the ones that survive and thrive in the future. Natural language allows you to write and create apps now, what’s left is human communication. Being able to communicate effectively to your customers (real customers, executives, directors, etc.) sets yourself apart … and it already does now too.

@android_poet @Keyur12901 Yes I think you are right here. We scalability is in view, I think proper separation of concern shouldn’t be overlooked

Yes, that’s a double-edged sword but handling nulls or empty states can become a nightmare. From my recent experience, it’s best to divide APIs as much as possible. If only three APIs are related to each other, avoid making additional network calls. Instead, create a separate ViewModel for them. This approach will make the system more scalable in the future.

• Keep the UI layer pure and side-effect-free. • Use a ViewModel (or separate state holders) to manage all UI state. • Perform expensive operations in the Repository layer away from the UI. • The UI should not care whether data comes from network, local DB, or a sync process. • Handle navigation in the ViewModel, using a clean abstraction create a Navigator.

@JorgeCastilloPr But some people still write that 🤣

Remember writing RecyclerViews and their adapters by hand?

@elonmusk @grok would you without bias elaborately counter what Elon said by giving an unbiased stand on who’s more trusted judging with who is is less distrusted ?

There you have it

@alexstyl You’re absolutely right 😎

It's actually for Compose UI but Jetpack Compose makes the algorithm happier

Cooking something very special for the Jetpack Compose fans

@WaivedSAP @malonso Great work dude. I think if you’re not a developer you shouldn’t be curious to try out new thing not even at this stage yet. There was never been a time that such depth graced anyone’s screen. It’s quite revolutionary!

Proud to be part of the team behind iOS26. Lots of fun new features like the redesigned text selection loupe. A malleable piece of glass that reacts to your movements and brings your content closer to you.

@alexstyl Nice one 👍

inb4 "is it written in Compose?" Yes! One part is. The SVG to Compose tool has been rewritten in Compose Web The rewrite was a breeze and I am so glad to get rid of the old HTML + jquery implementation. composables.com/svg-to-compose

The Composables website is now fully written in Kotlin! For a site focused on a Kotlin technology it was about time, don't you think? Thank god for AI that allows me to experiment like this. Otherwise I wouldn't have the capacity to rewrite a whole site to a different language this effortlessly. Went from mobile (android) to full stack so that I can build my own startups. Tried multiple techs and this one finally clicked. My backends are written in Kotlin/JS and my apps are written in Compose Multiplatform. If you spot that might be off, let me know!

One of the greatest forms of crime in our time won't be orchestrated with guns and bombs - it'll come through psychological hacks designed to exploit human vulnerability. - Prince Promise

@Windows I suddenly stopped hoping 😂

it’s always “when is Windows 12 coming” and never “how are you doing person who runs the Windows account”

@Sellmair How does this work?

🎉 Looking forward to feedback for Compose Hot Reload alpha06, which finally supports 'jar-based reloads' and async launch modes. github.com/JetBrains/comp…

@vitalisasiku @JameHealy @GoodyGambino @sama This is brilliant 👌

@JameHealy @GoodyGambino @sama Great callout. Applying coding principles (early exit) to llm this time with orders of magnitude savings in compute.

it's super fun seeing people love images in chatgpt. but our GPUs are melting. we are going to temporarily introduce some rate limits while we work on making it more efficient. hopefully won't be long! chatgpt free tier will get 3 generations per day soon.

@Sellmair Does this work on Jetpack Compose project not multi platform?

github.com/JetBrains/comp…: Compose Hot Reload now supports even more complex environments. Happy to announce: Hot Reloading UI now works when building and working on the IntelliJ IDE.

@DenisJeliazkov @sketch This is cool, really 😎

8) @sketch The OG Mac-native design tool that feels more polished than alternatives. The way it handles symbols, artboards & exports just flows naturally. I was forced to switch to Figma for collaboration, but Sketch still feels better to use. I miss it ngl.

I'm a design addict. Here are 8 of the most powerful UIs I've ever seen: 1) Apple's Dynamic Island

@AlexPierce114 I’m in 😁

@ruffydfire Whoever is responsible for this didn’t just torment an entire ethnic group; they also stunted the growth of a nation. It’s heartbreaking to think about what this country could have become if there had been a genuine, unified force for governance.

I know some ethnic bigots will be upset that Babangida debunked the Igbo coup narrative Let’s refresh their memories Ademoyega wrote a book called “why we struck”and he also said it was not an ethnic coup! Ademoyega was not an igbo man. The truth is bitter Why we struck was released in 1981. Facts are sacred. Sentiment is free Babangida was right. It was not an Igbo coup.

@paciosdev What did you work on?

All set, all done. Good luck to everyone who applied for the SSC, despite the result, the experience has been life changing for me.