Contact person: Customized Square Integrated Restaurant App

Phone:Show

Email:Show

Location: Melbourne, Australia

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"iOS & Android Restaurant App with Square (Login + Loyalty + Push)

About

We use Square Point of Sale / Square Online for all ordering & deliveries. I need a developer to build a branded iOS & Android app, publish it to App Store + Google Play, and integrate Square so customers can browse, order, and use Square Loyalty inside the app. We’ll keep the main commerce flow in a WebView to move fast, but I need a native login screen and proper push notifications.

⸻

Scope

1) Mobile Apps (iOS & Android)
• Clean, modern UI with my branding (splash screen, app icon, color scheme).
• Native Login screen (email/phone + OTP or password; discuss best approach).
• Main store experience loads my Square Online site via WebView (in-app browser), with:
• Deep links for menu, cart, checkout.
• Session persistence (keep users signed in where possible).
• Loyalty: Use the existing Square Online loyalty pages within the WebView (loyalty balance, rewards redemption).
• Push Notifications:
• Promotions (when we add/update promos in Square).
• Order updates (placed/accepted/out-for-delivery, where available).
• Use FCM (Android) + APNs (iOS). Handle device tokens & topic/user subscriptions.

2) Integrations & Tech
• Square ecosystem:
• WebView to Square Online for shopping/checkout.
• Loyalty shown inside WebView (no custom points engine).
• If needed for UX: use Square APIs (Catalog/Orders/Customers/Loyalty) only where they add value (e.g., showing user name/status on native home).
• Notifications plumbing:
• Create a small backend (Node/Express or similar) to:
• Receive Square Webhooks (e.g., catalog updates for promos, order status events).
• Map events to notification topics/users.
• Send via FCM/APNs.
• Provide a simple admin toggle to send manual promo pushes (optional but preferred).
• Deep linking:
• Support links like mybrand://menu, mybrand://loyalty, mybrand://orders to jump to key screens/sections.

3) App Store / Play Store Publishing
• Prepare listing assets: icons, splash, screenshots, short description, full description, keywords.
• Guide me (or handle) setup of Apple Developer & Google Play Console.
• Build signed releases, fix review feedback, and get both apps live.
• Handover: full source code, build instructions, environment variables, and minimal CI/CD (optional).

⸻

Deliverables
1. iOS app (ready & live on App Store).
2. Android app (ready & live on Play Store).
3. Native Login, branded splash, app icon set.
4. WebView store flow + Loyalty pages.
5. Push notifications (FCM/APNs) wired to Square events & manual promos.
6. Lightweight backend/webhook service with documentation.
7. Source code + README + env sample + publishing docs.

⸻

Quality & UX Requirements
• Smooth navigation (no visible “web” lag where possible).
• Handle offline/error states gracefully (retry, friendly messages).
• Persist session where feasible; fall back to Square Online login page inside WebView when needed.
• Respect Apple/Google policies (e.g., Sign in with Apple if using a third-party login—advise best practice).
• Privacy Policy & Terms screens (I will provide text; you wire up in-app & in store listings).

⸻

Milestones
1. Design & Architecture (wireframes for login/home; integration plan)
2. MVP Build (WebView store, login, basic push)
3. Webhooks/Notifications (backend + mapping tests)
4. Beta (TestFlight + Internal Test; bug fixes)
5. Store Submission (assets, compliance, review responses)
6. Go-Live & Handover (docs, code, quick training)

⸻

Acceptance Criteria
• Login screen matches brand and works end-to-end.
• Loyalty dashboard accessible via in-app menu and renders via Square Online WebView.
• Creating/updating a promo in Square (catalog/discount) can trigger a push to a test device/topic.
• Order status changes generate pushes where Square events are available (or clearly documented limitations).
• Apps approved & live; builds reproducible from repo; env config documented.

⸻

What You Provide
• Past examples of WebView-based apps with native enhancements.
• Any Square (POS/Online/Loyalty) integration experience.
• Proposed tech stack (e.g., React Native/Flutter vs. Kotlin+Swift) and why.
• Approach to login/session with Square Online (native pre-auth vs. in-WebView login).
• Hosting choice for the webhook backend (e.g., Render, [login to view URL], Vercel functions).
• Timeline & fixed price with milestone breakdown.
• Post-launch support terms (bug-fix window, update policy).

⸻

Constraints & Notes
• Keep core commerce in WebView to reduce custom build effort.
• Loyalty stays in WebView (no custom points logic).
• Push must be reliable (handle token refresh & opt-in/opt-out).
• I own the code and app listings.

⸻

Assets I Will Provide
• Logo, colors, brand guidelines.
• Privacy Policy & Terms URLs/text.
• Square Online URL and access needed for testing.
• Copy for app store listings (or approve yours).

⸻

Questions for the Developer (answer in your proposal)
1. Login: Do you recommend keeping authentication entirely within the WebView (Square Online’s customer account), or a native login that bridges sessions? Pros/cons?
2. Notifications: Your plan to map Square webhook events to FCM/APNs and to send promo pushes when discounts are updated.
3. Stack: React Native vs Flutter vs fully native—what’s your choice and why for WebView-heavy apps with push?
4. Compliance: Any App Store/Play Store pitfalls you foresee with WebViews and how you’ll address them.
5. Support: What’s included post-launch (e.g., 30–60 days bug-fixes)?" (client-provided description)