Where it started
Before Smart TVs, before streaming apps, there was the web. Over 10 years of frontend work. Responsive sites, dashboards, CMS-driven platforms, e-commerce, whatever needed building. The web is where we learned to care about performance, and everything since has been shaped by that.
What we are building now
We are currently building the web platform for one of the largest premium streaming services in the Middle East. A platform backed by a major Hollywood studio, serving millions of subscribers across the MENA region with exclusive content from top global studios.
The technical picture
The platform runs on Next.js and React 19. It supports full Arabic (RTL) and English (LTR) layouts with seamless language switching across the entire UI. Content discovery, playback, account management, and a multi-step subscription flow with real-time validation and OTP verification all live under one roof.
We built an in-house component library that is shared between the web application and the TV applications. Same design language, same interaction patterns, one source of truth. This lets us ship features faster on both platforms without duplicating effort.
On the content side, the platform integrates with a headless CMS for editorial content and streaming feeds through centralized API handling. DRM-protected video playback works natively in the browser with the same player pipeline we use on Smart TVs.
Earlier web work
Before the current project, we built a responsive website for a national broadcaster in the Middle East using React and SASS. We have also delivered internal dashboards, content portals, and marketing sites for enterprise clients across Turkey. Most of this work was done in-house for large organizations, so we can not name names. But the throughline is the same: fast, clean, built to last.
Performance by habit
Years of building for Smart TVs with 512MB of RAM made us obsessive about bundle size, rendering efficiency, and load times. That thinking carries directly into our web work. We measure everything, ship nothing unnecessary, and treat every kilobyte like it costs something. Because on a 3G connection in a rural area, it does.
Accessibility from the start
Building for TV remotes taught us that not everyone uses a mouse. We write semantic HTML, proper ARIA attributes, full keyboard navigation, and screen reader support. These are not afterthoughts. They are part of how we build.
Tech
React · Next.js · TypeScript · TailwindCSS · SCSS · Vite · Webpack · SSR/SSG · REST APIs · Headless CMS · RTL/LTR · DRM Playback · Responsive Design · Accessibility
Have a web project in mind? Get in touch.