Mobile applications
We build mobile apps that need to talk to something real: an ERP, a catalog, a member database, a payment system. React Native and Flutter on the front, a GraphQL or REST API we design on the back, and the business logic where it already lives.
Reviewed by Atul Makwana, CEO & Co-Founder, Heliconia Solutions · Odoo 16 Functional Certification · Odoo Partner · Updated
Businesses that run on what we built
Our position
Heliconia builds mobile applications that extend business systems: customer apps for a jewellery retailer's saving schemes, a supplier catalog app for a manufacturer, a member app for a medical association, a business-card platform with subscriptions. Every one connects to a real backend through an API we designed, and most of those backends are Odoo.
That is a narrower claim than "we build any app", and a truer one. The hard part of a business mobile app isn't the screens. It's authentication against the ERP, keeping catalog and stock in sync, handling payments, and shipping updates without an app-store release. That is where our work lives.
What we build
Product browsing, orders, subscriptions and payments on the ERP. Aria Jewellers' app enrols customers in gold saving schemes billed through Razorpay.
Catalog showcase, ordering and account tools for trade customers. Ramdev Kangan's Flutter catalog app on Odoo over GraphQL.
Profiles, content, jobs, messaging and push. Freiburger Bund's React Native app for physicians.
The mobile half of a web product, sharing its API. WaveContact's Flutter app.
Warehouse, service and sales tools on Odoo data for teams away from a desk.
Mobile storefronts on headless commerce backends.
Technical expertise
Architecture
The same API serves the web application. The business logic stays in one place.
iOS app
React Native / Flutter
Android app
Same codebase
Web app
Next.js: sharing the API
API layer
GraphQL / REST · OTP and token auth · push (FCM) · webhooks
Backend
Odoo (products, orders, customers, subscriptions) or a custom Node.js/Python service
Services
PostgreSQL · Redis · Meilisearch · Cloudflare R2 / S3 · payment gateways
Delivery
Users, platforms, the backend it extends, offline needs, payments, notifications.
Designed for the screens, with the backend team. Odoo modules or custom services built in parallel.
Flows and UI on the platform conventions, in a design system shared with the web app where one exists.
React Native or Flutter, with real API data from the first sprint and TestFlight / internal testing builds every iteration.
Device testing, performance on low-end phones, store submission and review handling.
OTA updates for fast fixes, store releases for native changes, monitoring throughout.
Evidence
Customer, member, supplier and SaaS apps, each on a backend we also built.
Jewellery retail & manufacturing
Multi-store fine jewellery retail and manufacturing on Odoo Enterprise: daily metal rates, RFID-tagged serialized stock, gold saving schemes with recurring payments, and a customer mobile app synced over GraphQL.
Healthcare association & career portal
A medical association platform where Odoo 18 Enterprise is the business backend behind a Next.js 15 web portal, React Native (Expo) iOS/Android apps, a Socket.IO messaging server and MeiliSearch: in German, English, French and Arabic.
Jewellery manufacturing
A bangle and fashion-jewellery manufacturer’s product catalog managed in Odoo and delivered to a cross-platform Flutter app over GraphQL, with media on Cloudflare R2 and production monitoring.
SaaS: digital business cards
Digital profile and contact-sharing platform where Odoo runs subscriptions, orders and the store behind a web frontend and a Flutter mobile app, with Stripe recurring payments, Google integrations and vCard export.
What clients say
Heliconia provided a unique canteen solution, saving us valuable ordering time. Their innovative approach has been invaluable to our operations.
Pradeep LakhaniBusiness Owner, Avasar AgencyHeliconia transformed our business with Odoo. They implemented a dynamic website with e-commerce capabilities, enhancing our online presence significantly.
Sandesh ThummarBusiness Owner, Ladder LogixQuestions
Cross-platform by default, React Native (Expo) or Flutter, with native modules where hardware, payment SDKs or OS features require them. One codebase, both stores.
Yes. We build a GraphQL or REST layer on Odoo shaped for the app, with OTP or token authentication and push notifications from Odoo events. Aria Jewellers, Ramdev Kangan and Freiburger Bund all run this way.
It depends on screens, backend work and integrations. Our production apps went from scope to first store release within their first engagement phase and have been evolving for 8-15+ months since. We give a real estimate after scope.
React Native when the team or product already lives in TypeScript/React and shares code with a Next.js web app. Flutter for catalog- and media-heavy apps or teams standardised on Dart. We run both in production.
Yes, for JavaScript-level changes on React Native via Expo over-the-air updates. Native changes still go through the stores.
Yes: accounts, listings, review responses and the release process for both stores.
Next step
Tell us what the app must do and what system it extends. We'll propose the platform, the API and a first release.