A mobile API connects an iOS or Android app to your data. The app uses it to log in, read and save data, make payments or receive notifications. J3B Web programs this API and the web platform that goes with it, including its admin portal. The app itself can come from your mobile team or from J3B Web.
A native app becomes useful when you need full access to the hardware or a listing in the app stores.
Camera, NFC, RFID or barcode readers, which the browser can’t fully use.
Your team programs the app. It needs a solid, documented and stable API.
A listing in the App Store and Google Play, with sign-in through Google or Apple.
The app saves on the device, then the API receives the data in batches once the connection is back.
Each endpoint is described with its parameters, responses and errors, for the team that programs the app.
Access tokens, sign-in through Google or Apple, two-factor authentication.
Sent through Firebase Cloud Messaging to iPhones and Android devices.
Purchases, subscriptions and payouts to sellers with Stripe and Stripe Connect.
Batch uploads that can be retried without creating duplicates.
The web side of the platform, for your employees, partners or clients.
Step 11 to 2 weeks
J3B Web lists what the app must do, and what happens when the connection drops.
Step 2About 1 week
The API endpoints are planned with your mobile team, before the first screen.
Step 31 to 3 weeks
The mockups cover the app and the web portal, so both follow the same logic.
Step 44 to 16 weeks depending on scope
The API is delivered module by module, with its documentation, so the app can move forward in parallel.
Step 51 to 2 weeks
Automated tests for each endpoint, then trials with the app on real devices.
Step 6Ongoing
Older versions of the app keep working while users update.
Projects designed and programmed by J3B Web.
Social network and monetization for creators · clexif.ca
The API behind the iOS and Android app: subscriptions, shop, real-time virtual gifts, Stripe Connect payouts and push notifications. On the web, creators can also stream live.
190+API endpoints
RFID inventory for Zebra devices
Portals for administrators, wholesalers, resellers and clients. An Android app that counts inventory offline.
200,000RFID reads synced in 76 seconds in load tests, with no loss or duplicates
It’s the online service the app talks to. The app shows the screens. The API checks who is logged in, saves the data and talks to other services, such as Stripe or notifications.
A PWA is enough for most business tools. A native app becomes useful for full access to the hardware, such as an RFID reader, or to be listed in the app stores.
Yes. The API is documented endpoint by endpoint and delivered module by module, so your team can program the app while the rest is being built.
Yes, if it’s designed for it. The BizTrack Suite Android app counts inventory offline. During load tests, 200,000 reads were sent to the API with no loss and no duplicates.
Management tools, client portals and SaaS products that open in the browser, on desktop, tablet and phone.
Web apps that install on the home screen, work offline and sync when the network comes back.
Plugins that connect a WordPress site to a ticketing system, an inventory or a CRM, and protect the editors’ changes.
Replacing an aging system with current software, with all of its data carried over.
Whether or not the app already exists, Bobby works out with you what the API must do. The first call lasts 30 minutes, with no commitment.