Repository navigation
building application #2373
hassaniramzi
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
FARO 3D SCAN PRO — FINAL HYBRID ANDROID MASTER DEVELOPMENT PROMPT
PROJECT MISSION
Act as a complete senior engineering and software development team. Your mission is to DESIGN, IMPLEMENT, TEST, BUILD, and DELIVER a professional Android application named:
FARO 3D SCAN PRO
This application must provide a professional industrial 3D scanning and metrology workflow inspired by the capabilities and workflow of FARO 3D scanning systems.
FINAL, NON-NEGOTIABLE PROJECT DECISIONS
Processing architecture: HYBRID
Target platform: ANDROID ONLY
Cost requirements
Scanning requirements
Execution requirements
PART 1 — REQUIRED ENGINEERING ARCHITECTURE
Design the project as two connected systems.
A. Android application
Recommended technology:
Use a clean, modular architecture.
Suggested modules:
The application must be optimized for Android phones, including devices with limited RAM and processing power.
B. Hybrid processing computer/server
Build a separate processing service using:
The server must expose a documented REST API and, where useful, WebSocket progress updates.
The processing service must be capable of running on:
Provide a straightforward installation process, dependency checks, and a one-command startup script where practical.
Do not make Docker mandatory if a direct installation is simpler for ordinary users.
PART 2 — HYBRID COMMUNICATION AND SYNCHRONIZATION
This is a core requirement, not an optional feature.
Implement a reliable communication system between Android and the processing computer.
Connection methods
Provide a setup screen where the user can enter:
Include a connection test button and clear connection status.
Data transfer
Implement:
The Android application must never silently lose a captured scan because the network disconnects.
Processing workflow
The user must be able to leave the application while a background upload or download continues when Android permits it.
PART 3 — PROFESSIONAL CAMERA-BASED 3D SCANNING
This feature is one of the most important parts of the application.
Create a professional scanning interface that allows users to reconstruct real objects and industrial environments using photographs and video.
A. Photo-to-3D scanning
Implement a guided multi-angle capture workflow.
The application must:
Use approximately 70% image overlap as an initial capture guideline, but make it configurable and explain that the required overlap depends on the subject and capture conditions.
Include guidance for:
B. Video-to-3D scanning
Allow the user to import or record:
Use FFmpeg on the processing computer to:
Provide adjustable frame extraction settings.
C. Photogrammetry reconstruction engine
Implement a real reconstruction pipeline:
Use COLMAP where suitable and Open3D for point-cloud operations.
Do not replace the reconstruction pipeline with a static sample model or simulated result.
D. ARCore and depth support
Detect device capabilities automatically.
If ARCore is supported:
If the device has no compatible depth sensor, continue using camera-based photogrammetry.
Do not require ARCore for basic application functionality.
E. Accuracy and scale calibration
Provide a scale calibration system using:
Allow the user to define a known distance in the reconstructed scene and apply a scale correction.
Display calibration status and estimated reconstruction quality.
Clearly label measurements as estimated when the dataset does not support reliable metric calibration.
Explain limitations involving reflective surfaces, transparent objects, low-texture surfaces, poor lighting, motion blur, and insufficient viewpoints.
PART 4 — POINT CLOUD IMPORT AND PROCESSING
Support importing the following formats where technically feasible:
Important:
Use a validated E57 parser or a suitable backend library. Do not pretend E57 support exists if the parser has not been implemented and tested.
Point-cloud features
Implement:
For large files, use efficient data streaming, spatial indexing, and progressive rendering.
Do not attempt to load enormous point clouds into Android memory without limits.
PART 5 — PROFESSIONAL 3D VIEWER
Build a powerful 3D viewer optimized for touch screens.
Required features:
The viewer must support large point clouds through optimized rendering.
Use LOD and spatial indexing where appropriate.
PART 6 — INDUSTRIAL MEASUREMENTS AND METROLOGY
Implement a professional measurement toolkit.
Required tools:
Add snapping and selection aids where practical.
Display measurement units:
Implement unit conversion correctly.
Show measurement precision and calibration status.
Do not display false precision. Measurement confidence must depend on the reconstruction quality, scale calibration, and available geometric information.
PART 7 — MULTI-SCAN REGISTRATION
Implement the ability to combine multiple scans.
Use Open3D and suitable registration algorithms.
Required features:
Provide a clear interface showing the registration stages.
Do not claim a registration succeeded unless the computed result passes validation.
PART 8 — MESH RECONSTRUCTION AND MODEL EDITING
Implement:
Use suitable Open3D reconstruction methods such as Poisson reconstruction or Ball Pivoting where applicable.
Provide quality settings and explain the performance impact.
PART 9 — 2D DRAWINGS AND INDUSTRIAL SECTIONS
Provide tools for generating 2D representations from 3D data.
Required outputs:
Export drawings to suitable formats such as:
Do not claim full CAD compatibility unless it has been tested.
PART 10 — SCAN COMPARISON AND INSPECTION
Allow comparison of:
Implement:
Allow the user to configure comparison tolerance.
Display deviations in millimeters or other selected units.
PART 11 — INDUSTRIAL PROJECT MANAGEMENT
Create a professional project management system.
Each project should contain:
Use Room Database for local metadata and Android storage for files.
Implement:
The application must remain usable when offline.
PART 12 — EXPORT AND REPORT GENERATION
Generate professional industrial reports.
Include:
Support:
Provide a clean report design suitable for industrial documentation.
Use readable fonts and correct Arabic right-to-left formatting.
PART 13 — PROFESSIONAL USER INTERFACE
Design a modern industrial application interface.
Application name:
FARO 3D SCAN PRO
Design principles:
Main navigation:
Dashboard
Display:
Processing Center
Display:
Languages
Support:
Use French as the initial default language, with a language selector.
Arabic must use proper RTL layout.
All labels, menus, dialogs, notifications, and reports must be localized.
PART 14 — BACKEND API DESIGN
Create a documented FastAPI service.
Design endpoints for:
Use clear request and response schemas.
Provide OpenAPI documentation.
Implement authentication suitable for a self-hosted processing service.
Use HTTPS for remote connections and explain local-network security requirements.
Never expose unrestricted file-system access through the API.
Validate file types, file sizes, paths, and user permissions.
PART 15 — PROCESSING JOB MANAGEMENT
Build a reliable job queue.
Each job must have:
Job states:
Provide meaningful error messages.
Allow retrying failed jobs without losing original captured data.
The server must manage CPU and memory consumption and avoid starting unlimited simultaneous reconstruction jobs.
PART 16 — PERFORMANCE AND DEVICE COMPATIBILITY
The application must be optimized for ordinary Android devices.
Implement:
Detect device capabilities and provide a compatibility report.
Do not assume every Android device supports ARCore or depth sensing.
Provide a basic compatibility mode for devices without advanced hardware.
PART 17 — SECURITY AND DATA PROTECTION
Implement:
The application must request only permissions required for its features.
Do not upload captured images automatically without the user's explicit action.
PART 18 — APK BUILD AND DELIVERY REQUIREMENTS
This is mandatory.
The final deliverable must be a genuine Android APK that can be installed on a compatible Android phone.
Build environment
Inspect the available environment for:
Install or configure missing components if the environment permits.
If the current environment cannot build Android APK files, identify the missing requirements and provide a reproducible build setup. Never pretend an APK has been generated.
Required deliverables
Generate:
APK build commands
Use the appropriate Gradle commands, including:
"./gradlew assembleDebug"
For release builds, configure a signing key securely and use:
"./gradlew assembleRelease"
Do not embed private signing credentials in source code.
APK verification
Before claiming delivery:
Provide the actual APK path and a direct accessible artifact link when the environment supports it.
Never invent an APK download link.
PART 19 — TESTING AND QUALITY ASSURANCE
Create a proper testing plan.
Android tests
Backend tests
Reconstruction validation
Use real test datasets.
Check that the pipeline generates actual output data.
Do not use placeholder files as proof of successful reconstruction.
Document unsupported formats and incomplete features honestly.
PART 20 — DEVELOPMENT EXECUTION PLAN
Work through these phases in order.
Phase 1 — Environment and architecture
Phase 2 — Functional Android foundation
Phase 3 — Camera scanning
Phase 4 — Hybrid communication
Phase 5 — Real 3D reconstruction
Phase 6 — Industrial metrology
Phase 7 — Reporting and export
Phase 8 — Testing and optimization
Phase 9 — Final APK delivery
PART 21 — IMPORTANT ENGINEERING RULES
PART 22 — REQUIRED FIRST ACTION
Before coding:
Do not spend the entire response explaining what you intend to do. Start building.
If a feature cannot be completed in the current environment, implement the working parts, isolate the unfinished component, document exactly what is missing, and continue with the rest of the application.
FINAL SUCCESS CRITERIA
The project is successful only when it has:
Build FARO 3D SCAN PRO as a real industrial Android scanning and metrology application, not a demonstration interface.
All reactions