Ahmed Ali

Ahmed Ali

Android Engineer at Infinum

Cairo, Egypt

Actions

I have been writing Android apps since the Eclipse days in 2012, combining over 13 years of professional and hobbyist experience. I'm also passionate about creating open-source tools that help developers and sharing knowledge to empower the community

Area of Expertise

  • Information & Communications Technology
  • Region & Country

Topics

  • Android Development
  • Android
  • Mobile Development

How We Moved from Android Studio to Slack

Our team ships fast. New features, bug fixes, hotfixes, all moving through the pipeline constantly. But we kept hitting the same bottleneck: QA finds a bug, opens a ticket, a dev picks it up, opens the project, makes the fix, opens a PR, waits for review. For small fixes this cycle felt heavier than the fix itself.

So we asked a simple question: what if QA could get a bug fixed without leaving Slack?

We built an AI agent that lives inside Slack. QA opens a thread with the bug details, a dev adds technical context if needed, and someone mentions the bot. From there, the agent reads the full thread, clones the repo, makes the fix, runs linters and tests, verifies the build passes, and opens a PR. No one had to open an IDE.

In the first 3 days on our first project, 20 bugs were fixed this way. Today it runs across 10 projects.

In this talk I'll walk through how we built this system and what we learned along the way:

• How we designed the agent to read Slack threads, understand context from screenshots and messages, and translate that into code changes
• Why we used Docker containers per job, with dedicated images for each platform (Android SDK, Flutter, .NET, Ruby) to keep everything isolated and reproducible
• The Android-specific challenges: Gradle builds inside containers, SDK setup, running verification without emulators
• Connecting the agent to external tools through MCP, and why authentication turned out to be one of the hardest problems to solve, especially with services like Figma
• What went well and what we'd do differently next time

From Idea to IDE: Developing Plugins for Android Studio

Android Studio allows developers to add custom features to make the IDE work better for their needs. In this talk, we'll look at how to use the Project Structure Interface (PSI) to create plugins that improve Android Studio and make development faster. We'll explain the basics of the Plugin SDK and show how Jetpack Compose can help build easy-to-use interfaces for these plugins. Attendees will learn about different kinds of plugins they can create and how these can help them work more efficiently in Android Studio. We'll also share examples of useful plugins to give you ideas and practical tips.

DroidKaigi 2024: https://youtu.be/3ID-W-X_5mw?si=9h59DXorAJ2nmY-C

Kotlin Multiplatform

Kotlin Multiplatform the current and the future state, How it works?, and how it is different from Flutter?

How the Ui works? Compose and SwiftUi

DroidKaigi 2026 Sessionize Event Upcoming

September 2026 Tokyo, Japan

droidcon Amman 2025 Sessionize Event

July 2025 Amman, Jordan

DroidKaigi 2024 Sessionize Event

September 2024 Tokyo, Japan

droidcon Egypt 2022 Sessionize Event

October 2022 Cairo, Egypt

Ahmed Ali

Android Engineer at Infinum

Cairo, Egypt

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top