What are the limitations of DEV3 Borrova I should know before buying?

Good to know

• Payments, SMS and push were not tested with live accounts. The Stripe, PayPal and Razorpay drivers, push notifications and SMS exist as drivers. 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 apps were not tested on physical devices. They build as a debug Android package and run on the iOS simulator. Expect to do your own end-to-end pass on a real phone once you point them at your server.
• Photos in the apps are generated tokens. The renter and owner apps send generated photo tokens for condition and claim photos rather than uploading pictures from the device camera. The API accepts real files, but the apps do not yet send them.
• Two owner features are missing from the API. There is no endpoint for owners to reply to a review (the owner app offers rating the renter instead) and no claims list for owners (the app builds its claims screen from returned bookings).
• Arabic is partial. It covers navigation and the main flows. Some long body copy stays English.
• Lighthouse mobile was not measured.
• Real-time: the apps refresh by polling, not a live socket.
• Scope: the deposit is a real charge, because the payment layer has no card pre-authorisation. Borrova does not verify identity documents automatically, staff review them.
• Name: Borrova is a working name checked by a web search only, not a trademark clearance. Check it before you launch under it.
• No hosted demo. All brands, people and items in the screenshots are fictional.