Living Museum of Learning
The Promise Is Part of the Product
Situation
Seven old Apple games had grown around different ways of connecting players.
Some were still using Nearby play. Three had now moved onto our new Internet Game Bridge:
Golden 24
Golden Xiangqi
Golden Army
On September 30, 2026, all three new versions were waiting for review:
Golden 24 4.1
Golden Xiangqi 2.1
Golden Army 2.1
The other four games were still Nearby.
Turning Point
The easy thing would have been to say:
“Internet works now. Keep moving.”
But we had made another promise.
Tomorrow, we would keep backward compatibility.
Not because a product manager put it on a roadmap.
Because once an infrastructure layer is shared by several games, changing it changes the world those games live in.
Emergence
We had just spent days building the smallest useful Internet Game Bridge we could.
The server knew rooms, players, mailboxes, and room lifecycle.
It did not know how Xiangqi worked.
It did not know how Army worked.
It did not know how Golden 24 worked.
The games knew what to do.
Then real testing found real problems.
A guest left and the host still remembered the old player.
A new guest joined but the host's stale room membership sent messages to the wrong player.
A host left and the guest received the room-ended signal but remained trapped in stale game UI.
We fixed them one by one.
And then we tested the uncomfortable case:
leave → join → leave → join → ...
It kept working.
That was the moment the infrastructure became something we could trust.
Learning
Software engineering is not only about making the newest thing work.
It is also about keeping promises made to the things that already exist.
A protocol is not finished when the happy path works.
It becomes real when players leave, rooms disappear, strangers join, old state becomes stale, and the system still tells the truth.
Theme
Backward compatibility is a promise.
What Is Possible?
Can one tiny game bridge eventually carry several completely different games?
How Does It Happen?
By keeping the server generic, the clients smart, and the protocol small enough to understand.
Why Does It Matter?
Because infrastructure is not merely code shared by applications.
It is a promise that tomorrow's change will not casually break yesterday's work.
Infrastructure is not merely code shared by applications. It is a promise that tomorrow's change will not casually break yesterday's work.