Waslni brings rides, parcel delivery, restaurants, groceries, shops, and wallet features into one branded customer experience. App Experience settings let each operator launch rides only, delivery only, or both—and choose which section opens first.
A super app can be a strong model for consumer mobility, but placing many unrelated modules on one home screen does not create a coherent product. The operator still needs a clear launch focus, reliable fulfilment, and a reason for customers to use each enabled service.
A practical approach is to begin with the service the market needs most, validate its operations, and add other modules when supply, support, and demand are ready. App Experience should follow that operating plan rather than force every module to appear at once.
Waslni is built for that sequence without forcing rides to remain the permanent core. In Settings → App Experience, an operator can choose Ride-only, Delivery-only, Ride-first, Delivery-first, or Both. Transport covers city rides and parcel jobs; Marketplace covers restaurants and grocery shops; Wallet is a separate optional feature. The same mobile app, quick in-app admin, and full web dashboard stay connected as the business model changes.
Customers book rides or parcel jobs from the Transport module. Approved drivers handle the work from driver mode in the same mobile app.
Customers browse restaurants and markets, build a cart, order, pay, and follow delivery from the same app.
Owners manage products, categories, options, offers, coupons, orders, live deliveries, wallet, API keys, and webhooks without installing a separate vendor app.
Permission-aware staff get quick operational tools in the app, while the web dashboard handles full dispatch, configuration, analytics, roles, payments, and audit history.
Running separate platforms for rides, delivery, and shops is three businesses. Running them on a shared backend is one operation with three customer-facing surfaces.
The same account can move between rider and approved-driver modes. Shop owners and authorised admins see their own tools in that app too.
Operators manage rides, delivery, shops, finance, and content from one admin console. Roles and permissions scope by module — your shops manager does not need ride-hailing access.
The wallet is independently switchable, and payment methods can be enabled for customers, drivers, or both according to the tenant country.
Operators approve shops and control commissions, timeouts, discovery radius, delivery offers, coupons, banners, and restaurant/market homepage sections.
Choose the preset, enable or hide modules, select the opening section, and localise module labels from the admin dashboard.
The web and in-app admin surfaces are permission-aware, so each team member sees only the operations assigned to their role.
A super app combines multiple consumer services — typically ride-hailing, food delivery, and shopping — in a single mobile app under one brand. The shared backend (drivers, payments, admin) makes operations cheaper than running multiple separate platforms. Examples: Gojek, Grab, Careem.
No. Choose Ride-only, Delivery-only, Ride-first, Delivery-first, or Both. Transport, Marketplace, and Wallet can be controlled independently, so the visible experience can grow with the operation.
Approved drivers use driver mode in the same mobile app. The dynamic service catalog and registration form determine which services, vehicle details, and documents apply to each operation.
No. Waslni uses one branded mobile app. A rider who becomes an approved driver switches the same account into driver mode; there is no second driver-app installation to manage.
Yes. When the marketplace is enabled, verified shop owners see a shop panel inside the same app for products, offers, coupons, orders, live delivery, wallet, team access, API keys, and webhooks.
Explore rides, marketplace delivery, shop operations, and administration in one configurable platform.