Conference App Specification Draft
Budget: €3,000 – €5,000 EUR
Conference App – Development Specification
1. Executive Summary
We are seeking a development partner to build a Conference Mobile App in both iOS and Android that focuses on user experience and seamless interaction with events. The app will serve as the primary digital companion for conference attendees, enabling event browsing, ticket onboarding, merchandise redemption, and engagement features such as music polling.
The core focus for this project is on the front-end mobile skeleton/template development and integrating this with pre-existing backend services provided through pre-existing APIs. The successful partner is expected to reuse a proven front-end mobile app skeleton/template for faster, more scalable, secure and more cost effective delivery. The vendor should use a proven front end mobile app template as a starting point to customize integration. The successful vendor should not be custom developing from scratch a mobile app front end.
The backend API and design assets will be provided. The vendor will only focus on the mobile app development using React Native, deploying on both iOS and Android, integrating with our backend APIs. The priority is to deliver a solid baseline architecture first, upon which features are integrated via REST APIs.
The successful vendor is expected to deliver:
• Proven mobile app front end template/skeleton in both iOS and Android as a starting point
• Customise this template to technical requirements below
• Integrate this template with APIs provided
2. Scope of Work
2.1 Baseline Mobile App Architecture & Template from which integration would be customized
The vendor must first deliver a solid, React Native using a proven template/skeleton, including:
• Navigation: React Navigation (stack + tab), with guarded routes and deep linking
• Authentication Flow: Login/logout, token refresh, secure storage
• API Layer: Centralized REST client (axios/fetch) with interceptors, retries, and typed DTOs
• Server State: TanStack Query ( or other REACT Query framework) for fetching, caching, pagination, retries, and invalidation
• Client/UI State: Zustand (preferred) or React Context for ephemeral UI state (toasts, modals, filters)
• Forms: React Hook Form + Zod for validation
• Theming & Styling: Design tokens for colors, spacing, typography; minimal placeholder UI acceptable
• Testing Framework: Jest + React Native Testing Library
• CI/CD: GitHub Actions or Expo EAS for automated builds & deployments
• App Distribution: Store submission scaffolding for App Store & Play Store
All features must be built as modular integrations plugged into this baseline architecture.
2.2 Core Features (Phase 1)
⚠️ Important: All core features are already built in the backend, ready for front end integration exposed via REST APIs. The vendor’s responsibility is strictly limited to integrating these APIs into the mobile app. No backend feature development or change is required.
The follow backend APIs will be provided which the front end must integrate with:
• Authentication & User Management (email/password, Google, Meta, WeChat)
• Event Content & Browsing (list, details, RSVP)
• Tickets (onboarding via API, list/details, dynamic QR codes)
• Merchandise (Shopify integration, wishlist, redemption)
• Music Polling (vote via backend API)
• Content Delivery (CMS API for text, images, descriptions)
• Payments (integration with TBD provider, modular implementation)
3. Technical Requirements
• Framework: React Native (Expo acceptable if justified)
• Platforms: iOS (latest 2 versions), Android (latest 3 versions)
• Backend: Existing REST API (provided)
• Authentication: Email, social login, WeChat OAuth
• Merchandise: Shopify Storefront API (or custom provided API)
• Payments: Modular adapter for TBD provider (Stripe, Adyen, PayPal, etc.)
• State Management Policy
o TanStack Query for server state (all API data)
o Zustand or Context for UI/local state
o Redux/RTK is not to be used unless justified/explicitly approved
• Forms: React Hook Form + Zod
• Storage: Secure token storage and Key Signing (Keychain/Keystore)
• Typing: Full TypeScript coverage for API DTOs and domain models
• Error Handling: Unified error boundary + user-friendly error states
• CI/CD: GitHub Actions or Expo EAS with automated builds
• Distribution: Ready for App Store & Play Store submissions
• Localization: Framework tool kit to support multi language.
• Security: code must be free from OWASP Top 10 vulnerabilities and integration must use industry best practice for security
4. Design & UX
• Deliver functional UI skeleton/template, not pixel-perfect design
• Use placeholder components where designs are not available
• Accessibility considered (legible text, contrast, screen reader basics)
• Maintain design token approach so Figma-driven styling can be applied later
5. Deliverables
• Baseline mobile app architecture and template (documented and delivered)
• React Native app for iOS & Android
• Integration with CMS API, Shopify API, Ticketing API
• Integration with pre-existing backend APIs:
• Authentication with email, socials, WeChat
• RSVP, ticket onboarding, QR code, merchandise, music polling
• Architecture Documentation: folder structure, state strategy, query key map, error handling
• Source code in client-owned GitHub repository
• Documentation: setup, build, API integration, architecture overview
• Test suite (unit + integration tests)
• CI/CD pipelines (GitHub Actions or Expo EAS) with variable placeholder for app submission on client owned account
6. Project Management
• Agile methodology (Scrum/Kanban)
• Weekly demos to client
• Issue tracking via Jira or GitHub Projects
• Direct Slack/Teams channel with client team
7. Timelines & Milestones
Phase 1: Baseline Architecture (Weeks 1–2)
• Repo, environments, CI/CD pipeline
• Navigation structure
• Authentication template/skeleton (login/logout/refresh)
• API client + TanStack Query setup
• Zustand/Context store for UI state
• Testing harness & design tokens
Phase 2: Feature Integrations (Weeks 3–n)
• Event browsing, CMS integration, RSVP
• Ticket onboarding + dynamic QR codes
• Merchandise integration + wishlist + redemption
• Payment provider integration (modular, TBD)
• Music polling feature integration
Phase 3: QA, UAT, and Store Prep (Weeks n – n+2)
• End-to-end functional testing
• Documentation finalization
• App store submissions (by client)
Note: n is to be justified by the bidder based on how much parallelization can be achieved
8. Budget & Commercials
• Fixed-price proposal with milestone-based payments
• Maintenance & support quoted separately
• Any Third-party costs (e.g. Shopify, notifications) must be stated at the start of the project
9. Evaluation Criteria-
• Proven React Native experience
• Proven reusable mobile app skeleton/template from which vendor will customize the integration
• Speed to delivery
• Portfolio of similar apps (events, ticketing, e-commerce integrations)
• Demonstrated experience with modern RN state management (TanStack Query, Zustand, React Hook Form)
• Timeline feasibility & proposed team structure
• Cost vs. value offered
• Ability to integrate WeChat login
10. Appendices
• API documentation (provided separately)
• Figma files (if available)
• Shopify API documentation link
• WeChat OAuth documentation link
1. Executive Summary
We are seeking a development partner to build a Conference Mobile App in both iOS and Android that focuses on user experience and seamless interaction with events. The app will serve as the primary digital companion for conference attendees, enabling event browsing, ticket onboarding, merchandise redemption, and engagement features such as music polling.
The core focus for this project is on the front-end mobile skeleton/template development and integrating this with pre-existing backend services provided through pre-existing APIs. The successful partner is expected to reuse a proven front-end mobile app skeleton/template for faster, more scalable, secure and more cost effective delivery. The vendor should use a proven front end mobile app template as a starting point to customize integration. The successful vendor should not be custom developing from scratch a mobile app front end.
The backend API and design assets will be provided. The vendor will only focus on the mobile app development using React Native, deploying on both iOS and Android, integrating with our backend APIs. The priority is to deliver a solid baseline architecture first, upon which features are integrated via REST APIs.
The successful vendor is expected to deliver:
• Proven mobile app front end template/skeleton in both iOS and Android as a starting point
• Customise this template to technical requirements below
• Integrate this template with APIs provided
2. Scope of Work
2.1 Baseline Mobile App Architecture & Template from which integration would be customized
The vendor must first deliver a solid, React Native using a proven template/skeleton, including:
• Navigation: React Navigation (stack + tab), with guarded routes and deep linking
• Authentication Flow: Login/logout, token refresh, secure storage
• API Layer: Centralized REST client (axios/fetch) with interceptors, retries, and typed DTOs
• Server State: TanStack Query ( or other REACT Query framework) for fetching, caching, pagination, retries, and invalidation
• Client/UI State: Zustand (preferred) or React Context for ephemeral UI state (toasts, modals, filters)
• Forms: React Hook Form + Zod for validation
• Theming & Styling: Design tokens for colors, spacing, typography; minimal placeholder UI acceptable
• Testing Framework: Jest + React Native Testing Library
• CI/CD: GitHub Actions or Expo EAS for automated builds & deployments
• App Distribution: Store submission scaffolding for App Store & Play Store
All features must be built as modular integrations plugged into this baseline architecture.
2.2 Core Features (Phase 1)
⚠️ Important: All core features are already built in the backend, ready for front end integration exposed via REST APIs. The vendor’s responsibility is strictly limited to integrating these APIs into the mobile app. No backend feature development or change is required.
The follow backend APIs will be provided which the front end must integrate with:
• Authentication & User Management (email/password, Google, Meta, WeChat)
• Event Content & Browsing (list, details, RSVP)
• Tickets (onboarding via API, list/details, dynamic QR codes)
• Merchandise (Shopify integration, wishlist, redemption)
• Music Polling (vote via backend API)
• Content Delivery (CMS API for text, images, descriptions)
• Payments (integration with TBD provider, modular implementation)
3. Technical Requirements
• Framework: React Native (Expo acceptable if justified)
• Platforms: iOS (latest 2 versions), Android (latest 3 versions)
• Backend: Existing REST API (provided)
• Authentication: Email, social login, WeChat OAuth
• Merchandise: Shopify Storefront API (or custom provided API)
• Payments: Modular adapter for TBD provider (Stripe, Adyen, PayPal, etc.)
• State Management Policy
o TanStack Query for server state (all API data)
o Zustand or Context for UI/local state
o Redux/RTK is not to be used unless justified/explicitly approved
• Forms: React Hook Form + Zod
• Storage: Secure token storage and Key Signing (Keychain/Keystore)
• Typing: Full TypeScript coverage for API DTOs and domain models
• Error Handling: Unified error boundary + user-friendly error states
• CI/CD: GitHub Actions or Expo EAS with automated builds
• Distribution: Ready for App Store & Play Store submissions
• Localization: Framework tool kit to support multi language.
• Security: code must be free from OWASP Top 10 vulnerabilities and integration must use industry best practice for security
4. Design & UX
• Deliver functional UI skeleton/template, not pixel-perfect design
• Use placeholder components where designs are not available
• Accessibility considered (legible text, contrast, screen reader basics)
• Maintain design token approach so Figma-driven styling can be applied later
5. Deliverables
• Baseline mobile app architecture and template (documented and delivered)
• React Native app for iOS & Android
• Integration with CMS API, Shopify API, Ticketing API
• Integration with pre-existing backend APIs:
• Authentication with email, socials, WeChat
• RSVP, ticket onboarding, QR code, merchandise, music polling
• Architecture Documentation: folder structure, state strategy, query key map, error handling
• Source code in client-owned GitHub repository
• Documentation: setup, build, API integration, architecture overview
• Test suite (unit + integration tests)
• CI/CD pipelines (GitHub Actions or Expo EAS) with variable placeholder for app submission on client owned account
6. Project Management
• Agile methodology (Scrum/Kanban)
• Weekly demos to client
• Issue tracking via Jira or GitHub Projects
• Direct Slack/Teams channel with client team
7. Timelines & Milestones
Phase 1: Baseline Architecture (Weeks 1–2)
• Repo, environments, CI/CD pipeline
• Navigation structure
• Authentication template/skeleton (login/logout/refresh)
• API client + TanStack Query setup
• Zustand/Context store for UI state
• Testing harness & design tokens
Phase 2: Feature Integrations (Weeks 3–n)
• Event browsing, CMS integration, RSVP
• Ticket onboarding + dynamic QR codes
• Merchandise integration + wishlist + redemption
• Payment provider integration (modular, TBD)
• Music polling feature integration
Phase 3: QA, UAT, and Store Prep (Weeks n – n+2)
• End-to-end functional testing
• Documentation finalization
• App store submissions (by client)
Note: n is to be justified by the bidder based on how much parallelization can be achieved
8. Budget & Commercials
• Fixed-price proposal with milestone-based payments
• Maintenance & support quoted separately
• Any Third-party costs (e.g. Shopify, notifications) must be stated at the start of the project
9. Evaluation Criteria-
• Proven React Native experience
• Proven reusable mobile app skeleton/template from which vendor will customize the integration
• Speed to delivery
• Portfolio of similar apps (events, ticketing, e-commerce integrations)
• Demonstrated experience with modern RN state management (TanStack Query, Zustand, React Hook Form)
• Timeline feasibility & proposed team structure
• Cost vs. value offered
• Ability to integrate WeChat login
10. Appendices
• API documentation (provided separately)
• Figma files (if available)
• Shopify API documentation link
• WeChat OAuth documentation link