Joined March 2014
- Tweets 16,583
- Following 1,792
- Followers 4,596
- Likes 20,815
2,531 Photos and videos
Pinned Tweet
Apr 20
Introducing Inware 7!
Material 3 Expressive πΈ
More animations β©
Tweaked transitions π«
Still made with love π«Ά
Inware could not exist without you, users, translators, and friends who helped me through the years. Thank you! β€οΈ
Download:
goto.evowizz.dev/inware
7
12
148
8,696
12h
Telegram be like π
19h
Android apps trying to implement Liquid Glass be like:
ALT image from @mehtababd
1
9
285
Jun 13
Woah, so all of this because of some Amazon employees... . That's wild.
Jun 13
The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees.
The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance.
Access to all other Claude models is not affected.
We apologize for this disruption to our customers. We believe this is a misunderstanding and are working to restore access as soon as possible.
Read our full statement: anthropic.com/news/fable-mytβ¦
2
330
Jun 10
Soon, Android Studio changelog will have a new format. They will appear in a tab :)
1
18
947
Jun 9
Difference between Apple and Meta is that if Meta removes AI from their products in Europe, European users will be happy.
Jun 9
JUST IN: EU orders Meta to allow rival AI chatbots free access to WhatsApp.
1
4
114
5,217
Jun 7
Yesterday I was made aware by @patrickmichalik of an issue in Android that's been there for years (since Android 12).
Static (non animated) splash screen icons are blurry. The issue is essentially caused because the icon is rasterized at 108dp and then scaled up to 160dp.
There's a workaround though! You can wrap your vector drawable into an animated-vector that essentially does nothing.
I created a ticket here: issuetracker.google.com/issuβ¦
12
14
483
41,613
Jun 5
Around a month ago I posted a ticket on Google's issue tracker asking for guidance on the experimental Style API.
issuetracker.google.com/issuβ¦
By default, styles can handle pressed, hovered, selected, enabled, and toggled states. But it doesn't handle a basic feature: visibility.
That is, if the Composable you create is meant to animate when it's visible, you have to handle this yourself. And that's fine! The problem is: docs do not cover this specific, yet somewhat common behavior.
My ticket has not be triaged at all. And I did send a DM to @riggaroo but the timing (around the Google I/O) likely did not help. cc @crafty
2
13
1,520
Jun 2
Honestly, now would be a good time for any messaging app to compete against Telegram. @signalapp is awesome, it really has everything in term of privacy. It's the best. But it lacks features. Merge Telegram features into Signal (without the NFT/Crypto BS/Propaganda), and you've got the perfect messaging client out there.
3
1
11
991
Jun 1
Check out @GetAviate, by @TechHighest π
Jun 1
'Aviate,' a Flighty-like app for Android, takes off with Play Store registration [Gallery] 9to5google.com/2026/06/01/av⦠by @nexusben
1
12
729
Dy πΈπ retweeted
May 30
βοΈ Aviate 1.0 prerelease is here! After 1.5 years of work:
β’ 30 bug fixes
β’ Brand new onboarding
β’ UI Redesigns
β’ Better uptime than GitHub
Pre-register now on Google Play and help us climb the charts, link below
10
8
85
32,532
May 29
We have to talk about Android Canary & Beta releases. I talked to a bunch of people here and there, and no one seems to understand what's going on. Both developers and users are confused.
Note:
Before I write about all of this, this post will indeed mention Android 17, but will go beyond Android 17.
-----
As of today, we have Android stable builds, Android Canary builds, QPR Beta builds, and next Android version Beta builds.
Let's see what the latest build of each currently are:
Stable: Android 16, API 36.1 (CP1A.260505.005)
Canary: Android 17, API 37.0 (ZP11.260417.009)
Next Beta: Superseded by QPR Beta.
QPR Beta: Android 17 QPR1 Beta 3, API 37.1 (CP31.260508.005).
Here's a list of all the issues I could see, both as a user, and as a developer.
Issues as both a user and a developer:
1. During the Google I/O, Android 17 RC1 was mentioned. What is this? We've never heard of it before and it was presented as if we were supposed to know about it.
Issues as a user:
1. You've released Android 17 QPR1 Beta without telling users if they should upgrade or not. Will the release of Android 17 be "QPR0", or will it be QPR1 (SDK 37.1) directly?
2. Will users having installed QPR1 have to reset their phone to switch to Android 17?
Issues as a developer (Hi @AndroidDev):
1. Android Canary was created to replace Developer Previews. They are meant for developers, yet Android Canary updates are missing API Diffs and references. Meaning that during all this time Android Canary builds, despite being meant for developers, they provide no advantage to developers in comparison to Android Betas. As a matter of fact...
2. The last Android Canary is older than the Android QPR1 Beta 3, but even when the last Android Canary was released it was already older than the Android QPR1 Beta 2. So what's the point of the Android Canary, if it's not a canary build?
3. The QPR1 is officially API 37.1 yet there's no official stable build of Android out there with API 37. Should developers target API 37.1 directly and skip 37 entirely? But also, API Diffs and references are missing for this API too. Where are they?
4. The SDK Manager in @AndroidStudio is a mess right now, especially if you've installed SDK Platforms that are now removed. It contains SDK 37.1-beta3, which we can install but don't have the docs of. 37.1-beta2, same thing. canary-20260413: still no docs. Multiple unversioned Canary Previews, etc.
2
17
1,195