n
neodigital5

Gbenga

@neodigital5

Fullstack Engineer Lovable app, Base44 app, Replit app, Supabase Postgresql

Nigeria
Inglés, Español, Alemán, Italiano, Francés, Holandés, Portugués, Danés
Parte de la información aparece en idioma inglés.
Sobre mí
Anyone can open DevTools on your app and copy your Supabase key. If your RLS is wrong, they can download every user you have. Most Lovable, Bolt, Base44, Replit and Cursor apps ship that way. I lock it down and make it production ready. Supabase security audits, RLS policies, exposed API keys, auth loops, edge functions, Stripe webhooks and white screen deploys on Vercel. You get a diagnosis in hours, a permanent fix, a screen recording proving it and a plain English report. AWS Certified DevOps Engineer. I work your timezone, day and night.... Lee más

Habilidades

n
neodigital5
Gbenga
desconectado • 
Tiempo medio de respuesta: 9 horas

Revisa mis servicios

Solución de problemas y mejoras
I will orioledb clickhouse lovable production edge function audit supabase rls postgres
Solución de problemas y mejoras
I will anon key supabase audit muse code productionize cursor ai app database security

Porfolio

Experiencia laboral

StatWellMD

Full-stack Engineer

StatWellMD • Freelance

Jul 2026 - Aug 2026 • 1 mo

A $29.99 telehealth visit only works if the intake flow works. There's no doctor on a video call to recover a confused patient, so every abandoned questionnaire is a lost sale and a person who didn't get treated. The interface is the consultation. StatWellMD is async urgent care. Pick a condition from 20+, fill out a symptom and history assessment in under five minutes, and a licensed US provider reviews it and sends a prescription to your pharmacy. No appointment, no calls, no insurance. I built the front end in React and TypeScript against the team's API. The work that decides whether this converts: Keeping a multi-step medical questionnaire from feeling like paperwork, with progress that's visible and answers that survive a back button or a dropped connection Condition discovery across categories and search, since a patient who can't find "UTI" leaves State eligibility surfaced early, because the service runs in 37 states plus DC and finding out at the payment step is the worst possible moment Mobile first, since most people start these at 11pm on a phone On a HIPAA platform there's also a rule the frontend has to hold on its own: no symptoms, conditions or identifiers in URLs, analytics events or local storage. That's how health apps leak without anyone attacking them.