Cyril Mottier
banner
cyrilmottier.com
Cyril Mottier
@cyrilmottier.com
Leadership, Engineering & Product amo.co. ex Zenly (Snap), CapitaineTrain.
Compile-time flagging is a game-changer for large codebases. Just be sure to expose these variants only at the highest level of your build. If you don’t, you’ll end up with combinatorial complexity leaking everywhere in your code.
January 21, 2026 at 5:31 PM
> We fixed a few minor bugs that were causing problems.

Thanks for that detailed changelog. Super helpful 🤦‍♂️
January 19, 2026 at 8:27 AM
Look who joined the meetup 😂
January 13, 2026 at 9:59 PM
🙈
January 13, 2026 at 7:53 PM
The @parisandroid.bsky.social is about to start. Let's begin with Compose magic 🤩
January 13, 2026 at 6:04 PM
Thrilled to meet the Android community tomorrow and dive into video generation, dependency injection, and compiler plugins!

Don’t miss out, register now: www.meetup.com/android-pari...
Meetup de Janvier chez amo 👑, Tue, Jan 13, 2026, 7:00 PM | Meetup
Bonne année 2026 à tous 🥳! On vous souhaite une bonne dose de Kotlin, d'Android, d'interfaces réactives & intuitives et surtout du code bien propre ✨! Pour commencer sur
www.meetup.com
January 12, 2026 at 7:07 AM
Join us with @ParisAndroidUG at @amoamoamo HQ on Jan 13, 2026! 🚀

On the agenda: generating videos off-screen and off-main thread from Composables, why & how we switched from Hilt to Metro DI, and how to build your own Kotlin compiler plugin.
January 6, 2026 at 10:00 AM
Big news. On January 13, 2026, amo is serving up something special for the @parisandroid.bsky.social 🚀. Think Metro DI insights and video magic from Composables. Stay tuned after the holidays for all the details!🍹
December 23, 2025 at 9:34 PM
Hidden perk of Metro DI over Dagger: no more wrestling with naming binding functions.

We’ve migrated nearly our entire codebase to @Contributed* annotations cutting thousands of lines of code in the process.
December 17, 2025 at 4:00 PM
My job isn't to design the perfect solution. It's to build the least flawed one possible.
December 9, 2025 at 7:55 AM
Websites like apilevels.com are useful, but nothing beats analyzing your own data. At amo, we see a radically different Android versions distribution. It completely shifts our decision process regarding usage of AGSL, AVIF, HEIC, and more.
November 25, 2025 at 10:47 AM
Tooling helps manage the complexity of large codebases. We built tools to track important metrics: ‘unused-modules’ to find deletable modules via DFS, ‘longest-path’ to calculate the longest dependency path - highlighting potential critical paths and more.
November 19, 2025 at 1:47 PM
Defying g̶r̶a̶v̶i̶t̶y̶ complexity
November 13, 2025 at 3:34 PM
The best code is no code
November 3, 2025 at 10:20 AM
Watched 'The Whale' last night. It made me cry, and I still get goosebumps rewatching the ending scene. Strongly recommended!
October 30, 2025 at 10:45 AM
I love enums/sealed classes/union types. I really do. They give exhaustivity at compile time ❤️.
But they just don’t scale. I always end up making the painful choice of trading compile-time safety for scalability. It hurts, but it’s necessary.
October 24, 2025 at 9:06 AM
Killing the game
October 23, 2025 at 7:14 AM
They don’t teach you this enough in CS school: graph data structures and algorithms are everywhere. Maps, social networks, build systems, object graphs, page ranking, you name it.
Master them, and you’ll unlock superpowers in problem-solving. 🚀
October 21, 2025 at 9:29 AM
> During an investigation, your job is not to fix issues, it is to understand root causes.

@p-y.wtf says (and does) it all…
p-y.wtf P-Y @p-y.wtf · Oct 21
I turned a leak investigation into a post on the Block eng blog to share a method that works well!

It's a bit long... I had to show how to encode code knowledge to automate leak investigations, and dig even deeper with YourKit Java Profiler.

engineering.block.xyz/blog/the-lea...

#AndroidDev
The LeakCanary Method
This blog post shares a method for root causing Android memory leaks
engineering.block.xyz
October 21, 2025 at 9:25 AM
Coupe d'Europe de la boulangerie. Pièce artistique de l'équipe française.
October 19, 2025 at 1:02 PM
A vital rule for scalability: every compilation unit must build in <15s (our threshold). Though build time ≠ LOC, tracking it reveals bloat, enforces discipline, and keeps your project fast as it scales. Speed is non-negotiable.
October 17, 2025 at 9:56 AM
In a highly modularized codebase, typing full Gradle task names can be tedious. Gradle supports task name abbreviation: just type the shortest unique prefix. If ambiguous, Gradle suggests candidates.

⚠️ Use locally for speed, but keep codebase references explicit for readability!
October 14, 2025 at 1:32 PM
5 ways motion elevates your product:

1️⃣ Emphasize information hierarchy
Guide attention effortlessly.

2️⃣ Add delight
Make interactions feel magical.

3️⃣ Provide feedback & status
Keep users informed in real time.
October 13, 2025 at 2:19 PM
Jeudi 16 octobre à 12h, je serai en direct avec Mathias de The Product Crew (TPC pour les intimes) pour parler engineering et produit ! Hâte d’échanger avec vous et de répondre à vos questions. À très vite !
October 8, 2025 at 6:39 AM
We built a custom animatable, collision-aware, collapsible annotation system on Google Maps. Huge UX improvement but we lost tilt support along the way.
We finally cracked the math and extended our projection calculations adding a whole new dimension to the map. Just gorgeous.
October 7, 2025 at 2:34 PM