Adrian Kajda

@Fuelio founder | Developer / AI | Google For Startups (Google Developer Launchpad) Mentor

[Adrian Kajda @adekk]

Fuelio is App of the Day on the App Store in the United States - Apple’s home market 🇺🇸🙀

Thank you Apple, the App Store team, and everyone using @Fuelio

#OnTheAppStore @AppStore #Fuelio #AppStore

[Adrian Kajda @adekk]

@hamen Look at the source and community note. Not worth even sharing this.

[Adrian Kajda @adekk]

@csinco @AndroidDev Yeah! I was waiting for that. Good job 👏

[Adrian Kajda @adekk]

@hamen @crashlytics Will check tomorrow. Just updating my app. It's always after release to Play Store (automatic tests probably). But for smaller apps - it's counting to your crashrate-free quota :)

[Adrian Kajda @adekk]

It shouldn't be just Antigravity. I'm still leaving in Android Studio (and XCode in parallel). But for Android Studio for me it's like 15y+.

Now the question is - if you want to build new AS based on IntelliJ or fork Antigravity. For me staying with JetBrains make sense more (at least now).

Strip what is not needed now and make agentic view better. For me - emulator needs to be always on.

I don't like switching right side (I know I can change it). Agent should be center view with all handy stuff Google showed yesterday.

I found myself running like 1-5 emulators (and physical devices).

I would focus more on emulator and views. But probably that's something @FMuntenescu was showing yesterday.

I wronte it in my other post. It's going in a right direction - you are not locking this to Gemini.

The core for me is - agent - subagents and emulator.

Agent should be able to show user skills loaded.

Already Android CLI + skills we have right now are awesome. I can't live without them.

Agent window should be default and we need grouped conversations with history. Just like the sidebar in Claude or Codex app (which is not optimal after 1 year). But it's good to have history, changes.

A little bit chaotic reply but we can move this discussion to a bigger group.

[Adrian Kajda @adekk]

It's interesting how Android Studio wasn't mentioned in the keynote. The tooling is changing, and I wonder what the future of Android Studio will look like.

I hope it won't end up being transformed into some Antigravity-Codex-like UI. That's something we already have.

But for sure, it needs to change and adapt to the new world.

What I like - and @matthewmccull started the keynote with this - is that they're not trying to lock you into their own harness and Google's models, like Antigravity does.

Today we're using Claude. In the past, Codex was more popular. In the future, maybe we'll switch to Google models. As we all know, depending on the projects we work on, we need to be able to switch between models and providers.

For some projects, I can't just use a Claude subscription. For private projects, I can play with any model (and that's how I'm working today - trying different models). For enterprise projects, I have to use the models I'm allowed to use.

I like how fast Android DevRel team is moving and in general how #AndroidDev is caching up with all that stuff that is going on in the dev area.

And well, I regret I coudn't make it to Mountain View this year 🥲

#AndroidDevSummit

[Adrian Kajda @adekk]

Yay! 🔥

[Mishaal Rahman @MishaalRahman]

✨ Gemini Nano 4, our latest on-device AI model, is available to developers through the ML Kit Agentic API.

With Nano 4, you can add an offline AI agent to your Android app.

#AndroidDevSummit

[Adrian Kajda @adekk]

New fear unlocked. At this point I'm not sure I should use Google models on account connected to the rest services at Google.

[Artem Russakovskii @ArtemR]

An update on this Gemini Google policy violation situation.

Thanks to two Googlers (@rodydavis, @_mohansolo) from the @antigravity team who reached out when my post started taking off, we were able to get to the bottom of it.

The 2 violation emails that I got were indeed related to Antigravity and to my attempt the previous day to do defensive research and find security bugs in our own codebase (https://t.co/pfNbuLkkdw).

From what I've gathered, the automated flags are indeed checked by some human team, and that team made a mistake and ended up confirming the flags rather than negating them.

The internal strikes on my account were reversed, so that I wouldn't be penalized for them in the future.

This experience seems to have kicked off an internal effort to improve their processes and prevent similar situations from happening in the future, but I don't know the specifics.

On my part, I've provided constructive feedback about concrete issues that can be improved (the fact that the notifications come after an unspecified amount of time following the activity, don't provide any hints as to what the activity that caused it was, are really vague, and mention unspecified services and content that may get restricted. There's nothing actionable in there, just generic help. It's a really jarring user experience.).

I'd like to thank Rody and Varun for springing into action, resolving this concern, and leading the charge internally to prevent it from happening in the future.

[Adrian Kajda @adekk]

@pelotasplus @FMuntenescu At least we know she's using Pixel 11 because then she got that "AI Pro" plan when Google is hiding latest models from you so she switched to Claude 😉

But that was another honest point in my opinion in today's presentation.

Good work @FMuntenescu. Nice demo!

[Adrian Kajda @adekk]

The agentic approach to Android development is huge, and I really like it! #AndroidDevSummit

Can't wait to get my hands on that "prototype" tool @FMuntenescu was showing and check it out!

I wonder how this will work without emulators. Even right now, I created my own workflow with emulators that is working great - but yes, it's sometimes slow a bit (especially for testing).

[Adrian Kajda @adekk]

My Pro sub for Codex ended. I switched to Plus to keep Access to models but right now. Sol, Terra. Nothing is working, same projects, super slow. And usage, I don't think you can even do simple tasks with Codex. Few prompts and it's gone. I'm super confused. I lived with my prv stuff in Codex for a long time. What happened?

[Adrian Kajda @adekk]

Fuelio is “Made for iPhone Duo” from Day 0. We released an app compatible with the new foldable iPhone even before the official premiere. It was a small-medium-sized task, but not that bad, because @Fuelio is a native app.

A few words about this. At first you might think: why do we need to support this? It’s a niche, a $2,000 phone almost no one will get.

Here’s why I think it’s worth it.

Starting in April 2027, whether you like it or not, you’ll have to publish screenshots of your app for iPhone Duo too. But the bigger impact, in my opinion, is that you’re not supporting just Duo. It’s a shared SDK, so many apps will also look better on iPad as a result. Not everything is shared, of course. Tablets don’t support the folding features. But the Duo UI is much closer to a tablet than to a regular phone, so it’s much easier to give the tablet version a better look too. And iPad is not a niche.

For years many developers ignored how their apps look on tablets. I was in that group. I only checked that the app looked OK, and that was all. I didn’t give the iPad any extra work. In most cases the target was iPhone. I think this will change now.

I’m not sure if this was the goal for @Apple and @AppStore Store. If not, it will be a nice side effect.

[Adrian Kajda @adekk]

@OrestesGaolin Super projekt! Sam budowałem sobię samochodową na podstawie OSM, ale tutaj 🔥 Nie ten poziom detalu.

[Adrian Kajda @adekk]

With that day 1. This is also a little bit complicated. Since my apps are Duo ready - I'm still waiting for Apple review that takes more time lately.

[Adrian Kajda @adekk]

In my opinion this will change quite fast. All of my apps are ready for Duo from Day 1.
Was it hard? Not so much if you use native stuff. It's getting more problematic if you don't use native. Then you need to adapt Apple's design language and just like Google Apps are using Material both on Android and iOS - it's problematic.

But I think it's a matter of time and don't forget - all apps starting April 2027 will have to put screenshots for Duo in App Store.

[Marques Brownlee @MKBHD]

The current state of apps on iPhone Duo: https://t.co/1jJt58zXN8

[Adrian Kajda @adekk]

@SeraAndroid That looks outstanding🔥 Great demo.

[Adrian Kajda @adekk]

Fixes are here but still we need to wait for your distro to put it in official repo.

[Dane Knecht 🦭 @dok2001]

PHP changes are live. Start patching. https://t.co/MyHFZgOZrc

Huge thanks to coordinated work by @ThePHPF!

[Adrian Kajda @adekk]

@dzienko @psmyrdek Od kilku lat (nawet już będzie 5 lat) wsparcie dla Pixeli czy Samsungów to 5-7 lat. Sporo się zmieniło na plus pod tym względem.

[Adrian Kajda @adekk]

@dzienko @psmyrdek O ile bierzesz flagowce to już się dawno zmieniło. W niskiej i średniej półce to nadal prawda.