NFC-Integrated Asset Installation App Development
Budget: $10,000 – $20,000 AUD
Job Title
Mobile App Developer Needed to Build Asset Installation Workflow (NFC + FileMaker Integration)
Project Overview
We are building a mobile asset lifecycle application, starting with a single, well‑defined Installation workflow.
An existing Claris FileMaker database already stores all asset, site, and metadata records.
This app will connect to that FileMaker system via API to read and update asset information during installation.
This phase focuses only on the Installation workflow used by onsite contractors.
Existing System Context
• Claris FileMaker is the system of record for all assets
• Assets already exist in the database prior to installation
• Each physical asset includes an NFC tag containing a unique identifier
• The mobile app will:
○ Read asset data from FileMaker
○ Update installation details back into FileMaker
Important:
This project does not require redesigning or restructuring the FileMaker database — only integration, working with the current Filemaker developer is required as part of this project.
Scope of Work (Installation Workflow Only)
1. Installation Flow (Mobile UX)
A guided, step‑by‑step workflow suitable for onsite use:
1. Installation overview screen (instructions + progress indicator)
2. Select installation date
○ Default to current date, with ability to backdate if required
3. Select site / location
○ Search and filter from FileMaker‑provided data
4. Scan asset NFC tag
○ Read unique asset identifier
○ Fallback: manual asset lookup from FileMaker
5. Capture installation photos
○ One or more images
6. Review & complete installation
○ Confirm and submit
2. NFC Integration
• Read NFC tags on supported mobile devices
• Extract asset identifier
• No complex tag writing required in this phase
3. FileMaker Integration
• Connect to Claris FileMaker via REST API
• Retrieve:
○ Asset records
○ Site / location data
• Update:
○ Installation date
○ Site / location
○ Photos / metadata
• Handle:
○ Offline use (local capture + sync when online)
4. Platform Expectations
• Mobile‑first (iOS & Android)
• Acceptable approaches:
○ React Native
○ Flutter
○ Native iOS / Android
• Clean, functional UI (branding and final design system supplied later)
Mobile App Developer Needed to Build Asset Installation Workflow (NFC + FileMaker Integration)
Project Overview
We are building a mobile asset lifecycle application, starting with a single, well‑defined Installation workflow.
An existing Claris FileMaker database already stores all asset, site, and metadata records.
This app will connect to that FileMaker system via API to read and update asset information during installation.
This phase focuses only on the Installation workflow used by onsite contractors.
Existing System Context
• Claris FileMaker is the system of record for all assets
• Assets already exist in the database prior to installation
• Each physical asset includes an NFC tag containing a unique identifier
• The mobile app will:
○ Read asset data from FileMaker
○ Update installation details back into FileMaker
Important:
This project does not require redesigning or restructuring the FileMaker database — only integration, working with the current Filemaker developer is required as part of this project.
Scope of Work (Installation Workflow Only)
1. Installation Flow (Mobile UX)
A guided, step‑by‑step workflow suitable for onsite use:
1. Installation overview screen (instructions + progress indicator)
2. Select installation date
○ Default to current date, with ability to backdate if required
3. Select site / location
○ Search and filter from FileMaker‑provided data
4. Scan asset NFC tag
○ Read unique asset identifier
○ Fallback: manual asset lookup from FileMaker
5. Capture installation photos
○ One or more images
6. Review & complete installation
○ Confirm and submit
2. NFC Integration
• Read NFC tags on supported mobile devices
• Extract asset identifier
• No complex tag writing required in this phase
3. FileMaker Integration
• Connect to Claris FileMaker via REST API
• Retrieve:
○ Asset records
○ Site / location data
• Update:
○ Installation date
○ Site / location
○ Photos / metadata
• Handle:
○ Offline use (local capture + sync when online)
4. Platform Expectations
• Mobile‑first (iOS & Android)
• Acceptable approaches:
○ React Native
○ Flutter
○ Native iOS / Android
• Clean, functional UI (branding and final design system supplied later)