Is there anything DEV3 Hagglo does not do?

Good to know

• Payments, SMS and push were not tested with live accounts. The Stripe, PayPal and Razorpay drivers, push notifications (FCM and APNs) and SMS exist as interfaces. The simulated gateway is the default, push and SMS use simulated or log drivers, and the money rules were tested against the simulated gateway only. Run your own test payments before taking real ones.
• The app was not tested on physical devices. It builds as a debug Android package and runs on the iOS simulator. It was tested against a built-in mock and against API responses captured from the backend, not against a live backend running behind it. Expect to do your own end-to-end pass once you point it at your server.
• Arabic is partial. It covers the main screens, not every string, and the Filament admin and account panels are not translated.
• Lighthouse was not run. The front-end size budget was measured (public JS and CSS 28.3 KB gzipped), but no Lighthouse scores were taken.
• Account actions have lighter tests. Pause, renew, mark sold, promote, pack and top-up in the web account panel have page-render tests; the API paths behind them are fully tested.
• Small gaps: price pins on the web map are not spread apart when they overlap.
• Scope: Hagglo does not take payments or arrange delivery between users. Money flows only for promotions, packs and wallet top-ups.
• Name: Hagglo is a working name checked by a web search only, not a trademark clearance. Check it before you launch under it.
• Real-time: the app refreshes an open chat every few seconds and the inbox less often; it has no live socket client.
• No hosted demo. All brands, people and ads in the screenshots are fictional.