API-Driven Booking Notification App
Budget: $20 – $30 NZD
I’m ready to turn a straightforward idea into a lightweight mobile app. The core task is simple: periodically call an external REST API, pull back a plain list of names, compare that list to the names the user has already stored in the app, and—when there’s a match—instantly push a notification to the user’s phone. No calendars, payments, or complex scheduling logic; just clean matching and reliable alerts.
Here’s the flow I have in mind. The user launches the app for the first time, enters or imports the names they care about, and moves on. In the background, a small service polls the API, parses the JSON, applies the name-match filter, and fires off a native push notification (Firebase Cloud Messaging / APNs) whenever a hit is found. A minimal settings screen lets the user edit their names and adjust how frequently the app checks the feed.
I’d love a cross-platform codebase—Flutter or React Native would be perfect—but I’m open to native if it cuts time. Either way, the hand-off should include:
• full source code with clear build instructions
• secure API integration (token or key handling)
• local storage for the user’s chosen names
• background polling and dependable push notifications
• a simple UI for name management and polling frequency
If you can layer in basic unit tests and a lightweight CI pipeline, that’s a bonus. Let me know your proposed timeline and any questions you need answered about the API, and let’s ship a clean MVP.
Here’s the flow I have in mind. The user launches the app for the first time, enters or imports the names they care about, and moves on. In the background, a small service polls the API, parses the JSON, applies the name-match filter, and fires off a native push notification (Firebase Cloud Messaging / APNs) whenever a hit is found. A minimal settings screen lets the user edit their names and adjust how frequently the app checks the feed.
I’d love a cross-platform codebase—Flutter or React Native would be perfect—but I’m open to native if it cuts time. Either way, the hand-off should include:
• full source code with clear build instructions
• secure API integration (token or key handling)
• local storage for the user’s chosen names
• background polling and dependable push notifications
• a simple UI for name management and polling frequency
If you can layer in basic unit tests and a lightweight CI pipeline, that’s a bonus. Let me know your proposed timeline and any questions you need answered about the API, and let’s ship a clean MVP.
Related categories:
PHP
Mobile App Development
iPhone
Android
React Native
Flutter
API Development
REST API