Tickle
SaaS - Frontend Architecture
A two-sided cleaning service platform needed to ship booking and operations flows to early users while reducing frontend instability and post-release defects.
I'm Sheshan Bandara, a senior engineer who has owned React frontend architecture for production SaaS used by real customers. If you want to hire a React developer to ship features fast without the frontend quietly turning to spaghetti, that's where I'm strongest.
I work across React, Next.js, TypeScript, Redux and Zustand, and Tailwind, with Vitest and Playwright coverage around the flows that matter. As a frontend engineer I focus on state boundaries, data contracts, and the test discipline that keeps releases boring.
Clear state and data boundaries so the codebase stays maintainable as the team and product grow, instead of becoming the file nobody wants to touch.
Improved Tickle pilot stability by adding Vitest and Playwright coverage for critical flows, reducing repeat UAT issues and post-release frontend defects
From SPA dashboards to server-rendered Next.js apps, with performance and accessibility built in rather than bolted on at the end.
SaaS - Frontend Architecture
A two-sided cleaning service platform needed to ship booking and operations flows to early users while reducing frontend instability and post-release defects.
EdTech - Microservices - Video
The legacy LVMS was difficult to scale and maintain. The UI/UX was outdated, playback was inconsistent, analytics and logs became unreliable under heavy data, and several workflows caused data inconsistency issues. Video uploads also took hours or overnight before lectures were ready to stream.
SaaS - Multi-tenant - Bilingual
A multi-branch institution needed one governed system for branch operations, finance workflows, alms scheduling, donor pledges, and data that had previously lived across logbooks. And a better way to guide visitors and share temple/place information without relying on printed boards or manual explanations.
Yes. A lot of my work is improving existing frontends: untangling state, adding test coverage, and stabilizing releases without a dramatic from-scratch rewrite.
My focus is web React and Next.js. I've shipped responsive web apps and an Electron desktop app, but native mobile isn't my lane, and I won't pretend it is.
It depends on your SEO and rendering needs. For marketing-visible or content-heavy products I lean Next.js; for internal tools a React SPA is often plenty. I'll recommend based on your case, not on what's trending this month.
Send a short note about the product and the frontend problem you're solving.
A few other selected ways I can help