Oleksandr M.

A dispatch platform running 1,878 jobs across 14 technicians in four languages - web dashboard, React Native app, multi-tenant backend, real-time sync between them. Built solo, end to end. That's the kind of thing I build. Most products don't break on the frontend - they break at the seam, where the admin panel was an afterthought and the mobile app and the web app disagree about the data. I build all three, so there is no seam. 7 years full-stack. Top Rated, 100% Job Success Score. Next.js, NestJS, React Native, Supabase, PostgreSQL. ▸ COMPLETE PRODUCTS Mobile app, admin dashboard, landing page, backend, database. One person, one architecture, one timeline. You're not coordinating three specialists and mediating their arguments about the API contract. ▸ ADMIN PANELS AND INTERNAL TOOLS Role-based access, data views that stay fast when the table has 200k rows, and the unglamorous parts that decide whether your team actually uses the thing instead of going back to spreadsheets. ▸ MULTI-TENANT AND SAAS Tenant isolation enforced at the database with Postgres row-level security, not in application code where a forgotten filter leaks another customer's data. Stripe billing with idempotent webhook handling. ▸ MOBILE 7 years of React Native, apps live in both stores, including the submission process and the rejections nobody warns you about. Also shipped: an e-commerce rebuild from 3.5s to 1.6s with all Core Web Vitals green, and a four-language platform where fixing SSR and indexing moved organic traffic within six weeks. Send me the codebase, the half-written spec, or just the problem, and I'll tell you honestly how I'd approach it. Updated: Mon 19 Oct 14:40