How free-devloper/faceapp works
Project type and purpose
• This is a full-stack mobile application (React Native, built with Expo) for face detection and recognition.
• It leverages Azure Cognitive Services (Face API) in the cloud to perform analysis and matching.
File structure
• Top-level files:
– App.js (entry point for the React Native front end)
– babel.config.js, package.json (build and dependency configuration)
– app.json, .expo-shared (Expo configuration)
• No custom backend code is present, which implies the mobile app communicates directly with Azure services.
README
• “A Simple face detection and recognition app in react-native with azure cloud services”
• Confirms the use of Azure Cognitive Services for core functionality.
a. Main components
1. React Native Mobile App (Expo)
2. Azure Cognitive Services – Face API
3. Azure Storage (optional, for storing reference face images or logs)
4. Azure AD / API Key Vault (for secure storage of credentials)
5. User device camera and UI layer
b. Relationships and interactions
– User taps “Capture” in the mobile UI → App invokes device camera
– App sends captured image via HTTPS to Azure Face API endpoint
– App fetches or displays recognition metadata (name, attributes)
– (Optional) App may upload or retrieve training images from Azure Blob Storage
c. Architectural patterns and design principles
– Client-driven interactions: mobile app is the “thick client” that orchestrates calls
– Serverless / PaaS approach: no custom backend servers, relying on Azure-managed endpoints
– Secure credential management: storing API keys or tokens in Azure Key Vault, not hard-coded
– Modularity: separate UI logic (App.js, components) from service clients (API wrappers)
d. Key technologies, frameworks, libraries
– React Native / Expo SDK
– axios or fetch for HTTP requests
– @azure/cognitiveservices-face (or direct REST calls)
– Azure Cognitive Services Face API
– Azure Blob Storage (optional)
– Azure Key Vault / Managed Identity (optional)