Embracing the future

We find ourselves at a pivotal moment in technology, akin to the early days of the App Store in 2008. However, the focus now is not on creating eye-catching apps but on developing invisible services that AI agents can interact with seamlessly.

As I retire from active duty USAF, I am preparing to transition to the tech sector in December 2026. This gives me a year to position myself effectively in a rapidly evolving landscape. If I spend this time honing my skills as a React UI developer, I may be preparing for a role that will be obsolete or irrelevant by the time I leave the military.

Here’s how I perceive the upcoming shift and how I am adapting my projects, GLXY, ck42x, to thrive in this new environment.

The Shift: From "Clicking" to "Invoking"

For the past 15 years, interacting with apps has followed a familiar routine:

Open the app.
Navigate through the menus.
Click buttons to execute tasks.

This process resembles manual labor, akin to factory work in the digital realm. The future, as outlined in recent discussions surrounding the Model Context Protocol (MCP), suggests a fundamental change. Instead of needing to access an app, users will express their intentions verbally, and the app will respond.

We are transitioning from a world dominated by Graphical User Interfaces (GUI) to one guided by Linguistic User Interfaces (LUI). In simpler terms, we are moving from physical actions to verbal commands.

My Strategy: "Agent-First" Architecture

What does this mean for developers like me?

The focus will shift from designing appealing interfaces to creating robust APIs that enable AI to perform tasks on our behalf.

I am embracing an "Agent-First" architecture in my projects:

The API is the Product: The frontend serves merely as one client. The main user could be an AI, like ChatGPT or Claude, acting on a human's behalf.
MCP Compliance: I am exploring the adoption of the Model Context Protocol, which informs AI systems about their capabilities, such as checking calendars or updating databases.
Next.js API Routes as Tools: My API routes are not just for data retrieval; they are crafted as specific "tools" for an AI agent to utilize.

The Tech Stack: Next.js + Supabase as the Foundation

The current tech landscape lowers the barrier for entry; there is no longer a need to master languages like Swift or Kotlin. Instead, a solid web service suffices.

This aligns perfectly with my choice of Next.js and Supabase:

Supabase: It offers structured data and vector embeddings for memory, which help agents comprehend context.
Next.js: It provides serverless endpoints that function as the agent's "hands."

I am not simply creating a web app; I am developing a "skill" for an omnipresent intelligence.

The 2026 Target

With my transition set for December 2026, I expect the "Agentic Commerce Protocol," which enables instant AI-assisted checkouts, to be fully established by that time.

I plan for GLXY and klutt3rbox to evolve into integrated services, not standalone destinations. I envision them operating within user conversations, delivering value where users are most engaged.

The Bottom Line

If your approach to app development remains unchanged from 2020, you are likely creating software that will soon be considered outdated.

The future favors those who build the underlying systems, not just the user interfaces. I am shifting my focus from attracting eyeballs to addressing user intent.

Are you adjusting your development strategy for this new "Agentic" future? I’d love to hear your thoughts.