Since submitting DropsEx, real usage has driven real improvements. Here's what's changed:
Fixed a live production bug Customers tracking their orders were occasionally hitting 401 errors. Root cause: the admin login session was bleeding into the public tracking page. Fixed by explicitly isolating session persistence between the admin and public Supabase client instances — two completely separate session contexts now, zero crossover.
Hardened database security Ran a full audit of Row-Level Security policies on the orders table — testing every access path directly: anonymous SELECT (should work, for public tracking), anonymous INSERT/UPDATE/DELETE (should fail, and does), and authenticated full access (works as expected for admin operations). Every policy confirmed locked down exactly as intended.
Paystack integration in progress Moving from manual bank transfer to in-app payment processing, so customers can pay directly at checkout instead of needing a separate step.
New on the roadmap: K-OBS (Klutch Only Best Sellers) The next feature we're designing: businesses using DropsEx will be able to list only their proven best-selling items — not a full catalog — organized by category (food, electronics, baking, and more). The idea is curation over catalog size, which matters in a market like Lagos where buyers are often overwhelmed by choice and inconsistent quality.
Launch approach will be tiered: businesses self-nominate a small number of top items at first (manually approved), moving toward a "Verified Best Seller" badge once enough order volume flows through DropsEx to back the claim with real sales data instead of self-reported claims. Honest about that limitation from day one — no false certification before the data exists to support it.
Still solo-built, still bootstrapped, still shipping. More updates as K-OBS moves from idea to build.
Log in or sign up for Devpost to join the conversation.