Sprint 8: Push Architecture and Native Notifications

After laying the foundation for multiplayer, ranking and matchmaking, Sprint 8 was about making Connect 3D feel truly real-time. This meant saying goodbye to constant polling and welcoming push-based architecture – where updates are delivered instantly, and players are notified the moment it’s their turn.

This was probably one of the most technically challenging sprints so far, but also one of the most satisfying.

From Polling to Push

Up until now, the client regularly asked the server: “Anything new?” – which worked for a few test users, but even then it’s not ideal. It wastes battery, uses unnecessary data, and introduces latency.

Now, Connect 3D uses WebSocket connections between client and server for real-time game state updates. When a player makes a move, the server pushes that change immediately to the opponent.

Implementing this required:

A persistent WebSocket service running in one of the microservices.
Game session and player connection tracking.
Error handling for disconnected clients and reconnection logic.

It took time to get right, but playing a game where your opponent’s move appears instantly – no delay, no refresh – is a night-and-day difference.

Native Notifications

WebSockets are great while you’re in the app, but what about when you’re not? I also integrated native notifications for both Android and iOS.

Now, if you’re not actively using the app and it becomes your turn, Connect 3D will notify you – just like any other game or messaging app. This required integrating:

Firebase Cloud Messaging (Android).
Apple Push Notification Service (iOS).

I also built backend triggers to send notifications when a move is made, and made sure everything is permission-aware and respects system settings.

Screenshot: First Connect 3D push notification on Android.

A Lot Under the Hood

This sprint involved lots of debugging, device testing and experimenting with different connection strategies. I tested on everything I could get my hands on: tablets, older phones, new phones, flaky Wi-Fi setups. Watching it finally work across the board felt incredible.

These changes may not be visible to players, but they completely change the way Connect 3D feels to play.

Photo: My messy desk with all test phones and tablets.

Next Sprint: Make It Beautiful (After a Break 😴)

Next sprint will focus on security, stability, and visual/audio polish:

Improve server-side validation and authentication handling.
Tighten API security and session management.
Redesign screens with new colors, buttons and texts.
Improve 3D models, textures and lights.
Add animations, transitions, and simple sound effects.

But first: I’ll be taking a well-deserved 6-week vacation. It’s been an intense few months and I want to come back refreshed and ready to bring the final polish that Connect 3D deserves.

See you on the other side!

– Elena