David

[Claude @claudeai]

Introducing Code Review, a new feature for Claude Code.

When a PR opens, Claude dispatches a team of agents to hunt for bugs.

[Sameer Samat @ssamat]

Building high-quality apps with LLMs demands AI that truly understands the Android ecosystem. That’s why we’ve introduced Android Bench, the official leaderboard for LLMs in Android development 🏆.

We’ve tested models against real-world tasks – from Jetpack Compose migrations to complex logic fixes – to help model creators identify gaps and accelerate improvements.

Explore the leaderboard and review our methodology: https://t.co/aVNMYbXQIl

[Allen Holub. https://linkedIn.com/in/allenholub @allenholub]

To me, the whole idea of managing scope is antiquated and not particularly useful. It assumes a fixed up-front plan from which you can deviate. It assumes a schedule based on that up-front plan. However, scope defined upfront does not work, and it never has. The notion also assumes project thinking, where you estimate based on that up-front plan. To me, all of this is dysfunctional.

It's best to figure out what to do next by doing the current thing (and getting feedback). Talk to your customers to figure out where to start. Pick the smallest core of the core of the core idea and build that. Get feedback. Use that feedback to decide what to do next. Release immediately to get revenue sooner. There are no projects. There is no "scope" to creep. There's just a continuous stream of added value. Stop when there's nothing valuable to add.

[Márton Braun (write-only account) @zsmb13]

The Android team has just released a brand new landing page for Kotlin Multiplatform, explaining the technology and showing how Google and JetBrains are support different parts of the ecosystem!

https://t.co/LxwEyTrqJ1

[Uncle Bob Martin @unclebobmartin]

A brief intro. Please RT. (or is it RX?)

[David @DavidGuerreroD]

I just published Compose Multiplatform: A ready-made Template for your next App https://t.co/b1WVmA5HB2

[Allen Holub. https://linkedIn.com/in/allenholub @allenholub]

I see no value in timeboxed "increments." Make the stories small and work on them until they're done, then work on the next one. I think the whole notion of a Sprint is one of the reasons Scrum (as usually practiced) is an utter failure—too much time is spent managing the Sprint and not enough time working. I see nothing good in a "timebox" or other artificial deadline. Motivate people by creating a great workplace, putting people first, and creating a culture of collaboration, respect, and pride in one's work. No need to bludgeon anybody with a timebox.

[Romain Guy @romainguy]

The Jetpack Compose team is hiring in London! If you'd like to join us, see https://t.co/QEJjOweLV0

[ProAndroidDev @proandroiddev]

An effective testing strategy for Android (Part 2) – Unit Testing. By @DavidGuerreroD #AndroidDev

https://t.co/54U7BOJIBv

[Alexey Alter-Pesotskiy @testableapple]

#40 issue of the Mobile Automation Newsletter is out 📬

🔗 https://t.co/hkFCDd5v0v

Thanks a mill @darryl_bayliss, @appforce1, @alexito4, @KaushalVasavaIn, @mustafayigitt_, @GargEtisha, @K_Rubaszewski, @luffyselah, @DavidGuerreroD, @riccardo_cardin, @olu_tayormi, @lfroms, @inyaki_mwc and more! 👏

Sponsored by @RunwayTeam 🙌

#ios #android #iosdev #androiddev #mobiledev #mobileapp #mobileappdevelopment #mobiletesting #mobileautomation #cicd

[David @DavidGuerreroD]

🚀 Ready to take your Android testing skills to the next level? Check out Part 2 of my series on building an effective testing strategy! This time, we dive deep into Unit Testing, covering best practices, test doubles, and more. 💡 #AndroidDev #UnitTesting https://t.co/4F7qibZ8Ud

[Martin Fowler @martinfowler]

Two decades ago, I posted that the strangler fig plant was an interesting metaphor for the gradual replacement of a legacy system. I haven't used the metaphor since, but many others did. I've rewritten the post focusing on how to make it succeed

https://t.co/RXx5LIdSrg

[Jose Alcérreca @ppvi]

🥳 We have just published more official guidance on testing!

Whether you optimize your app for different screens or not, you should verify that it works correctly on any device with automated tests.

And it's not just about adaptive layouts!

https://t.co/JPALmhO2C9

[Jorge Castillo @JorgeCastilloPr]

Here’s the list of types defined outside Compose that are known to be stable by the Compose Compiler.

Of course the compiler can infer other types as stable also. This is just a shortcut list for known stable types.

[Jose Alcérreca @ppvi]

Happy new year #AndroidDev! If you're starting out or need a refresh, here are 3 projects focused on architecture and testing:

🧵

[Fernando Cejas @fernando_cejas]

Hi everyone! I'm officially looking for a new #adventure :).

So if you need someone “all-terrain” (#IC, #Leadership area, etc) , I'm more than happy to #help/#contribute/#collaborate in any way I can. Please #ping.

RTs are more than appreciated. 🩷

https://t.co/c5DJnwf3Sj

[Donn Felker @donnfelker]

This week on @fragmentedcast, @kaushikgopal and I talk to @siggijons about the art of Android App Modularization.

Need to modularize your app? Struggling with an existing app structure? 🤔 Then this one is for you …

Check it out here: https://t.co/2s5S8bMcBD

[Donn Felker @donnfelker]

🚨 This week @kaushikgopal and I talk to @tfcporciuncula about Dependency Injection with Kotlin Inject on the @FragmentedCast 🎉

More info, links and listen in here 👇
https://t.co/iq9lpKtKe0

[Chris Banes @chrisbanes]

TIL that IntelliJ/Android Studio has a widescreen monitor setting. ↔

It lays out bottom docked panels to be displayed within any panels on the left/right. Basically, the bottom docked panels aren't displayed all the way on the edges now. I much prefer it.

[David @DavidGuerreroD]

Do you remember when you joined Twitter? I do! #MyTwitterAnniversary