My Smart City is a civic and household-services platform that lets residents report municipal issues, access local service information and book selected household services through web and mobile interfaces.
The product is materially beyond an MVP-only presence: core account, service-selection and checkout surfaces were directly exercised and the active app has substantial public distribution. Security and error-handling defects prevent a higher tier. Recommend Tier 2: direct functional evidence plus an active distributed mobile product support market-readiness, with validation/payment limitations noted.
The reviewer tested account creation, service selection, itemised checkout and a councillor-registration flow across web and mobile. Weak password acceptance and a raw Firebase authentication error were observed; payment was not completed.
The Android app is current, had 100K+ downloads at verification, and lists municipal issue reporting, service-provider booking and tracking. The official service remains active.
Weak password validation; raw authentication error surfaced to the user; payment loop not completed.
No completed payment or fulfilment transaction was observed.
These images formed part of the evidence pack considered during verification. Full-standard records retain the contributor's factual caption for each screenshot.
Earlier-standard evidence image — no contributor caption was stored.
Earlier-standard evidence image — no contributor caption was stored.
Earlier-standard evidence image — no contributor caption was stored.
Earlier-standard evidence image — no contributor caption was stored.
Earlier-standard evidence image — no contributor caption was stored.
Earlier-standard evidence image — no contributor caption was stored.
The verified result is the official public checkpoint record. For earlier-standard reviews, these findings may have been reconstructed from preserved evidence during Sandbox Africa’s 2026 audit; they are not presented as if the contributor originally completed a structured worksheet. Contributor-submitted checkpoint wording is shown only where explicit public reviewer attribution has been enabled.
Checking for dead links, infinite loading screens, or "Coming Soon" landing pages masquerading as live products.
The reviewer verified active web and mobile product surfaces.
Can a user or enterprise actually sign up, or is it gated behind broken "Contact Sales" forms?
Account creation and entry to the usable service experience were completed.
Does the application actually do what it claims to do? (e.g. a payment gateway completing a test transaction, a logistics app's routing engine working.)
Service selection, itemised checkout and councillor registration were exercised, but payment and fulfilment were not completed.
Assessing the logical flow, responsiveness, and basic accessibility of the platform.
Core journeys worked, but weak password acceptance and a raw Firebase authentication error created avoidable user-facing friction.
Load speeds, uptime reliability, and basic stress responses.
The reviewed web/mobile flows were accessible, but no controlled uptime or load test was performed.
Availability, clarity, and functionality of API documentation and webhooks.
No API or webhook integration workflow was independently tested in the submitted assessment.
SSL certification, basic encryption standards, and data handling transparency.
The reviewer observed weak password validation and an exposed authentication error; no deeper security assessment was completed.
Claiming verifies company ownership and enables a response or additional evidence. It does not permit editing of the independent review.
