The web was built around the assumption that you’ll always be connected.

I think we can build better than that.

Abdullah Teslim

Software Engineer, Frontend Infrastructure

Lagos, Nigeria

SOFTWARE ENGINEER · FRONTEND INFRASTRUCTURE

01 / STORY

I started with interfaces.

Then I became interested in what happens underneath them. What happens to application state when the network disappears, what happens to a request that fails halfway through, how a browser can hold onto something useful, and how an app can recover without forcing the person using it to start over.

That led me into browser systems, synchronization, persistent state, realtime communication, and distributed behavior across the client.

Eventually, I built something around it.

Software that keeps working

Modern web apps depend heavily on a network. That works until it does not. My work sits in the layer between the application and the server, making client side software more persistent, more resilient, and less dependent on every request succeeding immediately. Not by replacing the backend, and not by rebuilding the app. By making better use of what already exists inside the browser.

STATESYNCREPLAYREALTIMERECOVERY
CONNECTIONYOUR APP KEEPS RUNNING

02 / WORK

Flux

Client side infrastructure for making web applications resilient to unreliable connectivity, without replacing an existing backend. The goal is not another database, it is to make the browser a more capable part of the application.

  • Persistent state

    Application data stays available in the browser instead of disappearing on reload or a dropped connection.

  • Offline mutations

    Actions taken while offline are persisted and queued instead of simply failing.

  • Replay and recovery

    When connectivity returns, queued operations are processed and reconciled with the server.

  • Synchronization

    Client state stays in sync with the backend while accounting for changes made on either side.

  • Conflict resolution

    When local and server state disagree, the app has a defined way to detect and resolve it.

  • Realtime

    Works alongside realtime transports, not just traditional request and response APIs.

Want this in your own application, instead of just this portfolio? Flux is built to be dropped into any frontend that needs to survive a bad connection.

Explore Flux

This is not something you have to take on faith. Turn off your internet connection right now, scroll down, and fill in the contact form anyway. Refresh the page if you feel like it. Reconnect whenever you want. The message still goes out the moment you are back online. That is the whole experience.

03 / EXPERIENCE

2025 to Present

Software Engineer

TsWorldTech

Designed and built Flux from the ground up, covering persistent browser state, mutation processing, synchronization, replay, conflict resolution, realtime communication, service workers, and coordination across browser tabs.

2025

Full Stack Software Engineer

Digital Native

Built and maintained web applications across React, Next.js, Node.js, and MongoDB, covering frontend architecture, API integration, and reusable components.

2024 to 2025

Frontend Developer

Maradel Digital Solutions

Built production React applications and integrated REST APIs, working across application state, responsive interfaces, and maintainable frontend architecture.

LANGUAGES

TypeScriptJavaScriptHTMLCSS

FRONTEND

ReactNext.jsZustandReduxJotaiTailwind CSS

CLIENT INFRASTRUCTURE

IndexedDBService WorkersCache StorageWeb LocksPWA architectureBrowser APIs

STATE & SYNCHRONIZATION

Offline systemsPersistent stateMutation queuesReplayConflict resolutionSynchronizationEventual consistencyState reconciliation

REALTIME

WebSocketsSocket.IOServer Sent Events

BACKEND

Node.jsExpress.jsRESTGraphQLPostgreSQLMongoDBSupabase

TESTING

JestReact Testing LibraryUnit testingIntegration testing

TOOLS & DEPLOYMENT

GitGitHubVercelCI/CDnpm/yarnPostman

04 / CONTACT

Have something to build?

This form runs on the same idea as the rest of the site. Turn off your internet connection, write a message, and send it anyway. Instead of the request failing, it is saved locally and replayed the moment your connection returns.

TRY IT OFFLINE, IT STILL WORKS
CONNECTED
POWERED BY FLUX