🚨 Android 17 is here - pushing Android toward secure-by-default, adaptive-by-default.
Here’s what every serious Android engineer should know. 👇
www.linkedin.com/posts/anandw...
If you’re using DataStore in production, would you enable this immediately — or are you rolling custom crypto already?
#AndroidDev #Jetpack #AndroidSecurity #Kotlin #AndroidGDE
Follow @anandwana001.bsky.social — Android GDE 💚 | Sharing what really helps devs grow.
This is the kind of improvement that shows AndroidX is thinking about real production concerns — not just APIs. Security isn’t a feature. It’s a responsibility.
2️⃣ Key management is everything If you mess up Keystore integration or key rotation, you brick user data.
3️⃣ This keeps encryption at the boundary Which means your domain layer stays clean.
That’s good architecture.
🎯 What Android devs should pay attention to
1️⃣ Associated Data is currently null
If you want stronger binding, you can attach stable AD (like datastore name).
But change it later → and old data becomes undecryptable.
And if decryption fails?
DataStore throws a CorruptionException.
Which is exactly what it should do.
Security failures are treated as data corruption — not ignored.
That’s mature API design.
🚀 Why this is the correct approach
It uses AEAD (Authenticated Encryption with Associated Data).
Which means:
• Confidentiality (no one reads your data)
• Integrity (no silent tampering)
• Authentication (wrong key = failure)
Encryption becomes transparent and centralized.
No hacks.
No custom storage layer.
No breaking DataStore’s design.
On read:
• Read encrypted bytes
• Decrypt
• Pass plaintext to the original serializer
🧠 How it works (in simple terms)
A new AeadSerializer<T> wraps your existing Serializer<T>.
On write:
• Serialize your object → bytes
• Encrypt using Tink AEAD
• Store ciphertext
But here’s what I love about this implementation 👇
It doesn’t try to “magically secure” DataStore.
Instead, it wraps the Serializer.
That’s architectural elegance.
android-review.googlesource.com/c/platform/f...
🔐 DataStore is finally getting encryption support — and it’s done the right way.
AndroidX just added integration with Tink to enable encryption in DataStore.
Thread 👇
Follow @anandwana001.bsky.social - Android GDE 💚 | Sharing what really helps devs grow.
#androidDev #jetpackCompose
If you’re building Android, contributing to open source, or seriously exploring DevRel — let’s connect 🤝
More coming. Staying public. Staying honest.
💚
This is just month one.
The goal isn’t visibility.
The goal is impact, consistency, and trust — with developers and with the ecosystem.
1️⃣1️⃣ Revived Google Applied CS with Android program with latest codebase
github.com/anandwana001...
🔟 Connected co-GDE Android experts with the AndroidEngineers community
Because communities grow faster when knowledge flows freely.
A big thanks to belalkhan
9️⃣ Learned from a Cross-Tech GDE (Angular)
Understanding day-to-day GDE work, contribution patterns, and the DevRel mindset across ecosystems. A big thanks to @santoshyadav.dev sir
8️⃣ Started tracking Android open-source PRs
Sharing upcoming features on Twitter / Substack / Bluesky — so devs learn before releases, not after.
bsky.app/profile/anan...
7️⃣ Evolved AndroidEngineers into a proper free learning platform
A single-stop space for Android developers to learn, grow, and stay current.
www.androidengineers.in
6️⃣ Wrote a 2-part blog series
📘 “Offline-First Android System Design: A Complete Guide”
Focused on real-world architecture — not textbook diagrams.
androidengineers.substack.com/p/offline-fi...
5️⃣ Invited by two colleges for Android sessions
Sessions coming soon 👀
4️⃣ Gained clarity on the GDE journey ahead
Not just benefits - but how the program supports growth as an engineer, educator, and DevRel practitioner.
3️⃣Had deep conversations with Android GDEs from South Africa
Understanding how they create impact, contribute consistently, and grow as engineers and mentors.
2️⃣Met new people, new teams
Started building real relationships across the Android ecosystem, not surface-level connections.
One month in, instead of celebrating quietly, I chose something more important to show up and do the work.
Here’s what Month 1 really looked like 👇
1️⃣ Learned how the GDE community truly works
Beyond the badge - it’s about responsibility, contribution, and long-term trust.
🚀 One month as a Google Developer Expert (Android) - here’s what actually happened
12 January - I was officially selected as a
Google Developer Expert for Android.
Thread 👇
DSA shouldn’t live in console programs.
It should live inside real architecture.
Open source repo ↓
github.com/anandwana001...
Built using AI-assisted workflows ( @jetbrains.com Junie AI helped speed up scaffolding & refactoring) - while I focused on architecture, correctness, and performance.
That’s modern engineering.
Tech stack:
• Kotlin Multiplatform
• Compose Multiplatform
• MVVM + StateFlow
• Type-safe Navigation 3
• Material 3
Runs on Android + iOS.
