n
neodigital5

Gbenga

@neodigital5

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

Nigeria
Englisch, Spanisch, Deutsch, Italienisch, Französisch, Niederländisch, Portugiesisch
Einige Informationen werden in englischer Sprache angezeigt.
Über mich
Works in preview. Breaks in production. Auth loops on redirect, environment variables never load, row level security blocks every query, the deploy returns a white screen. I fix that layer. Supabase and Postgres, RLS policies, auth flows, edge functions, API keys and deploys on Vercel, Netlify and Railway. Apps built in Lovable, Bolt, Replit and Base44. You get: diagnosis in 1 to 2 hours, a permanent fix instead of a patch, a screen recording proving it works, and a plain English writeup of what broke and why. AWS Certified DevOps Engineer. I work your hours and overnight.... Mehr lesen

Kompetenzen

n
neodigital5
Gbenga
offline • 
Durchschnittliche Antwortzeit: 1 Stunde

Meine Dienstleistungen

Fehlerbehebung und Verbesserungen
I will lovable app production ready edge functions with a supabase security audit rls
Fehlerbehebung und Verbesserungen
I will do security audit, rescue your supabase backend nextjs app with postgresql rls

Portfolio

Arbeitserfahrung

StatWellMD

Full-stack Engineer

StatWellMD • Freiberufler

Jul 2026 - Aug 20261 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.