The Story Behind Bondi: How A Bored Couple Accidentally Built a Game

The funny thing about Bondi is that it was never supposed to exist.

There was no startup idea.

No product roadmap.

No market research.

No grand vision of disrupting the couples gaming industry. 😂

My wife and I were simply looking for something fun to do over the weekend.

Like most modern couples, our first instinct was to search online.

That search lasted longer than expected.

Every game felt slightly wrong.

Some were too serious.

Some were too generic.

Some felt like they were designed by a committee whose only goal was to squeeze every possible feature into a simple question game.

At one point I remember saying:

"Why does a game about knowing your partner need achievements?"

The answer is still unknown.

After opening and closing a ridiculous number of tabs, we reached the point most people eventually reach:

"We'll just manage with one of these."

But instead of managing, I had a different thought.

"What if we build our own?"

To be fair, this is probably not a normal thought.

Most people would pick the closest option and move on with their lives.

Unfortunately, I am not most people.

My wife looked at me with the same expression people reserve for children who announce they want to become astronauts after watching a movie.

You know the look.

The "that's cute, but let's be serious" look.

But this is where things got interesting.

Five years ago, that conversation would have ended there.

Neither of us are game developers.

Neither of us know how to build mobile games.

Neither of us were interested in learning game development that evening.

But AI changed the equation.

Suddenly the question was no longer:

"Can we build a game?"

The question became:

"Can we describe the game well enough?"

That is a very different problem.

So we opened Anything.com.

And then something fascinating happened.

For the next forty-five minutes, we did not code.

We made decisions.

What should the game feel like?

What kind of questions should it ask?

Should it be funny?

Should it be romantic?

Should it be competitive?

Should players get points?

Should they not?

What surprised me most was that the technical side became the easiest part.

The hard part was taste.

The hard part was deciding what to build.

That feels like an important lesson about AI.

People keep talking about AI replacing technical skills.

I think it is doing something more interesting.

It is moving value away from execution and toward judgement.

The bottleneck was not coding.

The bottleneck was us.

What do we actually want?

What should this experience feel like?

What should happen next?

Those questions still belonged to humans.

The AI just helped us move faster.

Of course, things were not perfect.

At one point we generated a version that looked like it had been designed during a power outage.

Another version asked questions that sounded like they came from a marriage counselling session.

One version was so serious that we almost felt guilty for laughing.

But eventually we landed somewhere we liked.

Not perfect.

Just ours.

That is probably my favourite part of this entire story.

Not the technology.

Not the speed.

The ownership.

The fact that an idea can move from:

"This would be nice"

to

"Here, try it"

in less than an hour.

That still feels slightly unreal to me.

Bondi is not a business.

It is not even a product in the traditional sense.

It is simply proof that the distance between an idea and reality is shrinking.

And if that is true for a random couple game built over a weekend, I suspect it will become true for a lot more things than games.

Including things we currently assume require experts.

Also, if you try Bondi and something breaks, please remember:

The development team consists of one husband, one wife, one bottle of whiskey, and several AI prompts.

Please adjust your expectations accordingly. 😂

Here is the link to the game: https://bondiapp.created.app

Till next time,

Your DMD