Geoffrey Métais
@geoffreymetais.bsky.social
Curieux, geek, ingénieur.
Senior Engineering manager Android chez Deezer
Senior Engineering manager Android chez Deezer
Reposted by Geoffrey Métais
Wanna replay the Deezer talk in your head? Here are the slides: www.slideshare.net/slideshow/th...
The journey from (not)REST to GraphQL at scale - The Deezer experience
A six-year journey at Deezer: from a tangle of legacy APIs to a unified GraphQL Gateway. A story of cross-team collaboration, Node.js performance tuning, and a few well-deserved slow claps from DevOps. - Download as a PDF or view online for free
www.slideshare.net
October 23, 2025 at 12:53 PM
Wanna replay the Deezer talk in your head? Here are the slides: www.slideshare.net/slideshow/th...
Do you think it's more efficient than Flutter or React Native?
(Considering the app scope is suitable for those frameworks)
(Considering the app scope is suitable for those frameworks)
September 13, 2025 at 8:23 PM
Do you think it's more efficient than Flutter or React Native?
(Considering the app scope is suitable for those frameworks)
(Considering the app scope is suitable for those frameworks)
It's a Thread.sleep() study. That explains all this Java boilerplate.
September 3, 2025 at 9:44 PM
It's a Thread.sleep() study. That explains all this Java boilerplate.
!! What happened to you? :)
September 3, 2025 at 9:16 PM
!! What happened to you? :)
Poke @liutikas.net , typical Gradle brainfuck.
How would a junior dev be supposed to manage that?
How would a junior dev be supposed to manage that?
August 21, 2025 at 2:05 PM
Poke @liutikas.net , typical Gradle brainfuck.
How would a junior dev be supposed to manage that?
How would a junior dev be supposed to manage that?
Arch Components arrived in 2017 too.
They drastically changed the SDK paradigm regarding development, and greatly helped to shift toward reactive programming.
IMHO they changed Android dev as much as Kotlin+Compose.
They drastically changed the SDK paradigm regarding development, and greatly helped to shift toward reactive programming.
IMHO they changed Android dev as much as Kotlin+Compose.
August 20, 2025 at 8:48 PM
Arch Components arrived in 2017 too.
They drastically changed the SDK paradigm regarding development, and greatly helped to shift toward reactive programming.
IMHO they changed Android dev as much as Kotlin+Compose.
They drastically changed the SDK paradigm regarding development, and greatly helped to shift toward reactive programming.
IMHO they changed Android dev as much as Kotlin+Compose.
Probably, I'm not even sure!
It would be more visible and more easily reachable on d.android.com directly IMHO.
It would be more visible and more easily reachable on d.android.com directly IMHO.
August 3, 2025 at 8:05 PM
Probably, I'm not even sure!
It would be more visible and more easily reachable on d.android.com directly IMHO.
It would be more visible and more easily reachable on d.android.com directly IMHO.
Developer guides*, of course.
Like a mini blog post for every common use case/ feature.
Like a mini blog post for every common use case/ feature.
August 3, 2025 at 8:00 PM
Developer guides*, of course.
Like a mini blog post for every common use case/ feature.
Like a mini blog post for every common use case/ feature.
My first guess would be "developer guided", for various use cases.
I love dev guides for code in Android documentation, it always greatly helped me.
And, the Gradle doc is not really accessible.
For every use case, the answer is "I should write a blog post for xxx".
Let's do it on d.android.com!
I love dev guides for code in Android documentation, it always greatly helped me.
And, the Gradle doc is not really accessible.
For every use case, the answer is "I should write a blog post for xxx".
Let's do it on d.android.com!
Android Mobile App Developer Tools – Android Developers
Discover the latest app development tools, platform updates, training, and documentation for developers across every Android device.
d.android.com
August 3, 2025 at 7:59 PM
My first guess would be "developer guided", for various use cases.
I love dev guides for code in Android documentation, it always greatly helped me.
And, the Gradle doc is not really accessible.
For every use case, the answer is "I should write a blog post for xxx".
Let's do it on d.android.com!
I love dev guides for code in Android documentation, it always greatly helped me.
And, the Gradle doc is not really accessible.
For every use case, the answer is "I should write a blog post for xxx".
Let's do it on d.android.com!
Is next week OK?
I'm on holidays right now.
I'm on holidays right now.
August 3, 2025 at 8:13 AM
Is next week OK?
I'm on holidays right now.
I'm on holidays right now.
Totally agree on this 👍
August 2, 2025 at 9:11 PM
Totally agree on this 👍
Look at Gradle 9 reception on reddit:
www.reddit.com/r/androiddev...
www.reddit.com/r/androiddev...
From the androiddev community on Reddit: Gradle 9.0 released
Explore this post and more from the androiddev community
www.reddit.com
August 2, 2025 at 9:10 PM
Look at Gradle 9 reception on reddit:
www.reddit.com/r/androiddev...
www.reddit.com/r/androiddev...
Average devs already struggle to develop correct (regarding architecture and performance) code, imposing an additional time consuming build system maintenance is very detrimental imho.
August 2, 2025 at 9:06 PM
Average devs already struggle to develop correct (regarding architecture and performance) code, imposing an additional time consuming build system maintenance is very detrimental imho.
Of course they add neat features but that's not my point.
They bring breaking changes too often, and too complex APIs also.
How many Android devs know what configuration cache is?
(I'm not even asking how many will handle it correctly).
They bring breaking changes too often, and too complex APIs also.
How many Android devs know what configuration cache is?
(I'm not even asking how many will handle it correctly).
August 2, 2025 at 9:04 PM
Of course they add neat features but that's not my point.
They bring breaking changes too often, and too complex APIs also.
How many Android devs know what configuration cache is?
(I'm not even asking how many will handle it correctly).
They bring breaking changes too often, and too complex APIs also.
How many Android devs know what configuration cache is?
(I'm not even asking how many will handle it correctly).
Slow pace doesn't mean no peace at all.
Slower pace = less friction, and hopefully less unnecessary API changes
Slower pace = less friction, and hopefully less unnecessary API changes
August 2, 2025 at 3:12 PM
Slow pace doesn't mean no peace at all.
Slower pace = less friction, and hopefully less unnecessary API changes
Slower pace = less friction, and hopefully less unnecessary API changes
It doesn't match the amount of time wasted on clueless buildsystem migrations, by a magnitude.
August 2, 2025 at 3:03 PM
It doesn't match the amount of time wasted on clueless buildsystem migrations, by a magnitude.
Why? Slower pace means less Gradle upgrades and more effective work!
August 2, 2025 at 7:51 AM
Why? Slower pace means less Gradle upgrades and more effective work!
Bonne chance Florian 🤞
July 29, 2025 at 2:58 PM
Bonne chance Florian 🤞