DEV Community: Khairunnisaas

Google I/O 2026 Dev Keynote: Recap

Khairunnisaas — Wed, 20 May 2026 08:43:17 +0000

In case you missed the Google I/O developer keynote today, here's a quick recap of the stuff Google announced.

And honestly... the overall theme this year is pretty obvious:

Google wants AI agents everywhere.

Like literally everywhere.

Most of the announcements today were either:

AI agents
tools for AI agents
workflows for AI agents
or tools that help AI agents make other tools

So yeah. Let's talk about it.

The Antigravity Ecosystem

Antigravity 2.0

Google officially introduced Antigravity 2.0, the new version of their AI development platform.

The easiest way to describe this thing is probably:
"mission control for AI agents."

Instead of just chatting with AI like normal, Antigravity lets developers orchestrate multiple agents, workflows, cloud resources, tools, and all that enterprise stuff in one place.

For enterprise users, it also connects directly to Google Cloud projects and automatically follows the permissions and security policies your company already has.

Basically Google is trying to make AI agents feel like actual teammates now.

Which is both cool and slightly terrifying.

Antigravity IDE

Because Antigravity is now heavily focused on "agentic workflows", Google also introduced something called Antigravity IDE.

And honestly?

This just feels like the original Antigravity app but specifically for coding.

I still don't fully understand why Google didn't just keep everything inside one app and make separate modes for:

coding
agent workflows

But okay I guess.

The whole point of Antigravity IDE is basically AI-assisted coding where developers and agents work together directly inside the editor.

So yeah... Google is REALLY pushing this "AI pair programmer" future.

Antigravity CLI

Google also announced Antigravity CLI.

From what they showed during the keynote, this honestly just looks like Gemini CLI but rebranded.

Google didn't really explain the differences properly on stage either.

But here's the interesting part:
Google already published a migration guide from Gemini CLI to Antigravity CLI.

So... yeah. Gemini CLI is probably getting deprecated eventually.

You can read the official migration update here:

Google’s migration update for Antigravity CLI

And again... I still don't understand why this couldn't just be an update instead of a whole new product name.

Google naming strategy remains undefeated.

Android Development Is Getting The AI Agent Treatment Too

Google also announced a bunch of Android-related AI tooling.

Android CLI + Android Knowledge Base

Google officially brought Android support into Antigravity through something called Android CLI.

This tool basically helps AI agents prepare Android development workflows automatically.

One of the biggest features here is the Android Knowledge Base — a constantly updated source of official Android documentation, APIs, and best practices.

Meaning the AI agent can fetch updated Android guidance directly while working on your project.

Google also introduced something called Android Skills.

These are open-source skills that help LLMs better understand Android codebases and execute more complex workflows correctly.

Google's internal team claims this uses 70% fewer tokens and completes tasks 3x faster. But obviously that's based on Google's own internal benchmarks.

Migration Agent

Okay honestly?
This was probably one of the coolest demos from the keynote.

Google showed something called Migration Agent.

The idea is simple:
you can migrate your existing app into a native Kotlin Android app.

React Native?
Supported. ✅

Web framework?
Supported. ✅

Even iOS apps apparently. ✅

Still early and still experimental, but if this thing actually works well, it could save developers an insane amount of time.

Web Updates

Modern Web Guidance

Google also announced something called Modern Web Guidance.

This is basically a collection of AI-ready frontend development best practices specifically designed for AI agents.

And honestly... this is actually needed.

One of the biggest problems with AI-generated frontend code right now is that the AI LOVES recommending outdated APIs, weird old patterns, or browser features from 2017.

Modern Web Guidance integrates directly with Baseline so agents can understand which modern web features are actually safe to use across browsers.

So hopefully we get less cursed AI-generated frontend code in the future.

Hopefully.

WebMCP

During the Modern Web Guidance demo, Google also introduced something called WebMCP.

Quoting to Google's docs:

"MCP is a proposed web standard to help you build and expose structured tools for AI agents."

But in simpler words:

WebMCP basically lets websites explain to AI agents how they should interact with them.

Imagine opening a complicated dashboard or settings page and instead of manually configuring everything yourself, you just tell Gemini:

"Set this thing up for me."

And the AI actually understands how to navigate the website properly.

That's basically the direction Google is trying to push here.

Still experimental though.

Google said the experimental MCP APIs will start trials in Chrome 149.

HTML-in-Canvas API

Last thing worth mentioning:
Google introduced HTML-in-Canvas API.

This API lets developers put actual DOM elements inside canvas.

Which sounds small...
but is actually a huge deal for accessibility and interactivity.

Because now those elements are:

searchable
selectable
accessible
compatible with browser features
better for SEO

This could become really useful for browser games, editors, design tools, and basically any heavy canvas-based web app.

And yeah... that's pretty much the biggest stuff from the developer keynote.

Overall, the direction is super clear now:
Google is going all-in on AI agents. And Antigravity is basically becoming the center of that ecosystem.

OpenAI Firing Drama In A Nutshell

Khairunnisaas — Tue, 21 Nov 2023 07:57:41 +0000

Hey y'all, how you doing?

Are you a fan of AI world? if that so... this might be one of a juicy article for you

TL;DR
[Friday 17/11/2023] Sam Altman got sacked. Greg Brockman quits
[Saturday 18/11/2023] OpenAI renegotiate with Sam
[Sunday 19/11/2023] Emmet Shear appointed to be Interim CEO for OpenAI
[Sunday 19/11/2023] Sam Altman and Greg Brockman got offer from microsoft to leading new AI research team
[Monday 20/11/2023] OpenAI employee rebelling to resign and joining Sam & Greg team in Microsoft or the boards resign and reinstate Sam & Greg

A few days ago Sam Altman (CEO of OpenAI) is getting fired for unexpected. As the Mr. Altman stepping down from his position, Mira Murati (CTO of OpenAI) was appointed to be an interim CEO of OpenAI, effective immediately.

In OpenAI blog about leadership transition, it says that

Mr. Altman’s departure follows a deliberative review process by the board, which concluded that he was not consistently candid in his communications with the board, hindering its ability to exercise its responsibilities. The board no longer has confidence in his ability to continue leading OpenAI.

From that statement, it looks like the Boards and Sam Altman had a different vision.

With the departure of Sam Altman from OpenAI, it looks like the employee got Sam Altman's back. On Twitter (Or X, whatever you called it), Sam Altman post a twitted "I love OpenAI team so much". That tweet got many replies from employee of OpenAI that shows their supports for Sam Altman.

// Detect dark theme var iframe = document.getElementById('tweet-1726099792600903681-779'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1726099792600903681&theme=dark" }

One hour after Sam Altman's tweet, Greg Brockman (Co founder of OpenAI), is posting about something too. With Sam Altman's leaving OpenAI, Brockman was supposed to move to another role. But, because of what's happening back then, he was to upset to stay and said that he quits from his position. Madness.

// Detect dark theme var iframe = document.getElementById('tweet-1725667410387378559-110'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1725667410387378559&theme=dark" }

Oh yeah, I almost forgot to mention. With the Sam leaving and Greg's gone, the employee of OpenAI is rebelling because too much is changing. (yeah well.. who likes it?)

On Saturday, the boards of OpenAI try to renegotiating with Sam for possible comeback. Well, appearently the negotiations didn't work out, and weird things happend. All of the sudden, Emmet Shear (former CEO of Twitch) is appointed to be interim CEO of OpenAI.

// Detect dark theme var iframe = document.getElementById('tweet-1726470504867913730-467'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1726470504867913730&theme=dark" }

Few hours after the news of Emmet Shear joining OpenAI, another big news happened. Satya Nadella (CEO of Microsoft) announce on his tweets that Sam Altman and Greg Brockman will be joining Microsoft and leading a new AI research team.

// Detect dark theme var iframe = document.getElementById('tweet-1726509045803336122-953'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1726509045803336122&theme=dark" }

By the way, Microsoft is not only offering a position for Sam and Greg, they offer to the whole of OpenAI team. They did this on purpose to push back the boards and try to calm the situation.

There's a letter from OpenAI employee to express how the feel for past days. In that letter it said that the all of employee in OpenAI is choose to resign and join the new position on Microsoft run by Greg Brockman and Sam Altman (as they get the offer too), or they will stay at OpenAI, but all the board members resign and reinstates Sam Altman and Greg Brockman

Pure Chaos.

so that's the news i've know so far, i'll keep it update if there's latest news from it. And sorry for the bad writing.

peace ✌

First Week Of HacktoberFest

Khairunnisaas — Mon, 09 Oct 2023 03:31:18 +0000

Hi Everyone! 👋

How's your first week of Hacktoberfest going? Is it going well, or just so-so? Have you received any accepted pull requests yet?

Don't worry if you haven't received an accepted PR yet; you're not alone.

Now, I want to share what I've accomplished so far during this Hacktoberfest.

First of all, I got one of my PRs accepted! You can check out the issue I raised here

By the way, if you're still unsure where to contribute to open source during this Hacktoberfest, I suggest checking out EddieHubCommunity on github. EddieHub has one of the most welcoming communities for newcomers, and the people there are very friendly and helpful.

Now, let's get back to my journey.

It's truly exciting to have my PR accepted, especially since this is my first time participating in Hacktoberfest! However, I do have some observations to share.

Let me tell you something...

Many people seem to have lost sight of the true purpose of Hacktoberfest. This event is meant to be about collaboration, not competition. Unfortunately, I've seen many individuals rushing to get assigned to issues that already have assignees or even creating pull requests for specific issues they weren't assigned to. I understand that everyone aims to complete four accepted PRs, and I'm no exception. However, it's crucial to remember that it's not just about being the first to get four accepted PRs. It's about the quality of your contributions. Are they valuable? Do they truly solve a problem? Have you learned something from what you've done?

It's about quality, not quantity.

Additionally, for this Hacktoberfest, I'm not only planning to contribute to open-source projects. I want this month to be all about coding. So, for this week, I plan to continue working on my personal project (hopefully, it will be finished soon, and I can share it with you).

And that's a wrap, folks. Thanks for reading my article. I hope you have a fantastic day!

My Pledge For Hacktoberfest

Khairunnisaas — Mon, 02 Oct 2023 07:15:28 +0000

Intro

Hi! My name is Nisa. I'm a Frontend developer, and also a newbie open source contributor.

Pledge

I pledge to be more active into dev / any programming community and be helpfull to each other!

Also, just did my first pull request for hacktoberfest! (still not merged tho) maybe i'm gonna make a mini article soon 🔜

My First Open Source Contributions

Khairunnisaas — Wed, 23 Aug 2023 03:37:24 +0000

Hey Folks! 👋

So... For the last past month i've been reading other people post about their contribution to the open source project. And i've been asking myself "Why am i never contribute to any open source project?" i mean... you can't lose anything by helping other people right? Instead, you will gain new knowledge. you might learn something from other people (and you will).

By inspired from other people journey about contributing to open source, i want to do it to, so.. i'm searching what kind of project i could possibly to contribute. and then i found a website from a post at freecodecamp called firsttimeronly. and in that website, there's a bunch of resources you could contribute for an "open source newbie" like me! And then i found a github repo called firstcontributions. That repo is meant to help the beginners to make their first contribution.

To contribute to that "project" is very easy. you just need to fork the project -> clone it -> create new branch -> add your name to the Contributors.md file -> create a pull request

That's it! 😎 very simple right?

and some of you might think "Just adding my name to the one of the file? that's very unneccessary". Yeah, That's true. But, if you not start with something small, how do you think you could start with something big? everything will start with small things, and it'll get bigger as the time flies.

OK, let's get back after creating my pull request. a few minutes later, i got the notification that my PR is accepted! and oh my god... i got so excited! you know the feeling you get after you achieving something you never done it before? yes, that feels good right? i know my first contribution is useless / unnecessary. but i really hope this is the beginning of my journey to be more active contributing to open source projects

That's it from me folks! Thank you for reading my little journey

New Way To Write Transform Properties In CSS 🙌

Khairunnisaas — Fri, 12 May 2023 02:44:00 +0000

A few days ago, Google held its annual event to introduce the latest updates on its products, Google I/O 23. There were many cool things announced, but one of my favorites was the individual transform property in CSS.

What is Individual Transform Property?

In CSS you can add movement to your component by adding transformation. Such as translation, rotation, scalling, etc. And usually you write transform property in CSS like this:

div{
  height: 60px;
  width: 60px;
  background-color: green;
  transform: translate(50%, 70%) rotate(30deg) scale(1.2);
}

But with Individual transform property, you can specify transform properties individually, like this:

div{
  height: 60px;
  width: 60px;
  background-color: green;
  translate: 50% 70%;
  rotate: 30deg;
  scale: 1.2
}

This individual transform property will come in handy when you're writing a complex keyframe, like making animation. As an example, you want to make animation that translate on 0% and 100%, and rotate the element from 25% to 85%. In the past, you have to calculate manually value for that 2 transformation at the different keyframe points.
The code will be look like this:

div{
  height: 60px;
  width: 60px;
  background-color: green;
  animation: anima 5s linear 2s infinite;
}

@keyframes anima{
  0%{ transform: translateX(0);}
  10%{ transform: translateX(10%) rotate(72deg);}
  25%{ transform: translateX(25%) rotate(90deg);}
  85%{ transform: translateX(85%) rotate(180deg);}
  95%{ transform: translateX(90%) rotate(240deg);}
  100%{ transform: translateX(100%) rotate(360deg);}
}

But with individual transfrom property, you don't need to calculate in between points. Just simply write values for individual property.

div{
  height: 60px;
  width: 60px;
  background-color: green;
  animation: anima 5s linear 2s infinite;
}

@keyframes anima{
  0% {rotate: 0;}
  25%, 85% {rotate: 180deg;}
  100% { rotate: 360deg;}

  0% {translate: 0 0;}
  100% { translate: 100% 0;}
}

As you can see, the code much easier to read and manage if you want to add more transformation. But you need to know that is individual transform property is only support on browser like:

Chrome: version 104 (and above)
Microsoft Edge: version 104 (and above)
Mozilla Firefox: Version 72 (and above)
Safari: Version 14.1 (and above)

Although it is currently only supported on the latest versions of popular browsers, it is an exciting development that will undoubtedly streamline the process of web design.

Happy Coding, And Stay Creative