Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Freelance · Socket.IO

Freelance Socket.IO developer for live maps, messaging and dispatch

I am one senior engineer who builds real-time features on Socket.IO. In TaxiDex it keeps dispatchers and drivers in the same live state, and in SessionBird it carries messaging inside a Flutter app. I work remotely on the server channels, the clients and the proxy between them.

Who hires a freelance Socket.IO engineer?

  • Teams with a live map, a dispatch screen or a chat that works in the demo and gets flaky in production.
  • Founders adding real-time updates to an existing Node.js API.
  • Mobile teams whose Flutter client and Node.js server disagree about what state is current.

What do I do with Socket.IO?

  • Live dispatch stateSocket.IO keeps dispatchers and drivers looking at the same jobs in TaxiDex, while the server stays the one place where fares are worked out.
  • Messaging in a mobile appSessionBird's messaging runs over Socket.IO into a Flutter client built with BLoC and get_it.
  • Server and client togetherI write the Node.js side and the Flutter side, so a mismatch between them is fixed in one place.
  • Behind nginxReal-time connections go through nginx in production, so timeouts and upgrade headers are set for sockets as well as for requests.
  • Real time next to jobsSocket events sit beside BullMQ queues and schedulers, so slow work leaves the live path.
  • Checked on the live systemI test real-time behaviour against the deployed server, since a local run does not show the proxy.

Which Socket.IO problems am I usually called in for?

  • Connections drop after about a minute

    A proxy timeout closes quiet sockets, and clients reconnect in a loop that looks like an app bug.

    The step-by-step fix
  • Polling requests return 404

    The path or proxy rule for the Socket.IO endpoint does not match what the client asks for.

    The step-by-step fix
  • The browser blocks the connection with a CORS error

    The server allows the web origin for ordinary requests but not for the socket handshake.

    The step-by-step fix
  • The client says io is not defined

    The client script is not loaded from where the page expects it.

    The step-by-step fix
  • The handshake fails with a 400

    A proxy or a version mismatch rejects the upgrade before the connection starts.

    The step-by-step fix

How does working with me on Socket.IO work?

  1. Send the connection logThe client and server log lines and your nginx location block. I reply within 24 hours.
  2. A call on the live partsA call within 48 hours on what must update live and what can poll.
  3. A written scopeServer events, client handling and proxy settings, in writing with what waits.
  4. Two-week sprintsKickoff is typically inside two weeks, and each sprint ends with a live feature running behind your proxy.
  5. Checked on the live systemProduction changes start with a backup and a tested rollback, and I watch real connections afterwards.

What do people ask about Socket.IO work?

Do you work with plain WebSockets as well?

My production work is on Socket.IO, and the proxy and timeout problems are the same ones you meet with plain WebSockets.

Can you add live updates to an API that already exists?

Yes. I add the real-time layer next to the existing routes and check it behind your proxy.

Do you build the mobile client too?

Yes. SessionBird's Socket.IO messaging is part of a Flutter app that I built.

Why does Socket.IO return 404 on the polling request?

The request is not reaching a Socket.IO server. I wrote a fix page on it: check which HTTP server it is attached to, the path and the proxy.

Proof

Products I built with Socket.IO

All projects

Own product · Taxi dispatch SaaS

TaxiDex

My own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.

TypeScriptNode.jsAdonisJSNext.js

SaaS · Customer engagement

SessionBird

An omnichannel engagement suite in Flutter: campaigns, chatbot, tickets, analytics and live calling.

FlutterDartBLoCSocket.IO

Next step

Need a senior Socket.IO engineer?

A discovery call within 48 hours, and a kickoff typically inside two weeks.