Imagine changing your app's behaviour... without changing the code. (Part 2)
lnkd.in·7h·
Discuss: DEV
Flag this post

Recently, I posted my "Event-Driven AI" experiment. I presented it as a "Rules Engine," but I've realized that was just scratching the surface.

After playing with it more, I just unlocked its real potential. 🤯

The video shows at first, a simple to-do app.
But by changing a single prompt (no code!), the app instantly becomes:

  • A Recipe Todo App (generating ingredients)
  • A Trip Todo App (generating a packing list)
  • A "Whatever-you-want" App

Recently, I posted my "Event-Driven AI" experiment. I presented it as a "Rules Engine," but I've realized that was just scratching the surface.

After playing with it more, I just unlocked its real potential. 🤯

The video shows at first, a simple to-do app.
But by changing a single prompt (no code!), the app instantly becomes:

  • A Recipe Todo App (generating ingredients)
  • A Trip Todo App (generating a packing list)
  • A "Whatever-you-want" App

Demo video

I realized I wasn't just building a "rules engine." I was building a "Generative UI Engine." 🤯 🤯

The LLM acts as a new layer of abstraction. Instead of me, the developer, hard-coding every feature, I just give the AI a "Swiss knife" of tools (like addTitle, addItem, setCounter).

The AI then uses these tools to build whatever the user wants, not just what the developer had in mind.

It's a shift from "Here are the 3 features I built for you" to "What do you want to accomplish?" 🤯 🤯 🤯

Yes, there are drawbacks (performance, determinism). But the potential for truly dynamic, user-centric applications is HUGE. This is the discovery that has me excited.

And the best part? I got this working in just a few hours, on the first try.

GitHub: https://lnkd.in/drKdTcVn

Similar Posts

Loading similar posts...