Loading case study
Busy
AMDailyActivity
React Native mobile app for daily Account Manager activity reporting, admin task management, and field evidence capture.
Role
Mobile Engineer
Timeline
2024
Platform
React Native
Focus
Activity + Task Management
Overview
AMDailyActivity is a React Native mobile app for recording daily Account Manager activities and helping Admin Marketing manage operational tasks. The app supports field reporting with GPS location, selfie evidence, environment photos, partner data, and role-based mobile workflows.
Problem
Daily activity reporting and task monitoring can become difficult when records are handled manually or across separated tools. Admin teams need visibility into task progress, while field activities need valid supporting evidence such as location and photos.
Solution
I helped build a role-based mobile workflow where Account Managers can submit daily activities with client, partner, location, selfie, and environment photo data, while Admin Marketing can create tasks, review task progress, cancel tasks, update task details, and create task-related activities.
Role
Mobile Engineer (React Native)
Timeline
2024
Stack
React Native 0.72TypeScriptReact NavigationRedux Rematch + PersistReact Native PaperAxiosFormik + YupReact Native Geolocation ServiceReact Native Image PickerMoment.jsJest
Requirements
Functional & non-functional
Functional
- Login and session persistence
- Role-based navigation for Account Manager and Admin Marketing
- Activity list with date filtering
- Create activity with GPS location, selfie, environment photo, partner, and description
- Team list for reviewing selected team member activities
- Admin task list with status filtering and sorting
- Create task from project or prospect data
- Task detail with progress and status
- Cancel task with cancellation reason
- Admin activity management with task selection and progress update
Non-functional
- Reliable validation for required evidence
- Responsive mobile input flow for field usage
- Clear loading, empty, and error states
- Role-safe navigation and action visibility
- Stable persisted session state
- Maintainable screen, service, store, helper, and reusable component structure
System Design
Architecture + data flow
Architecture
The app is structured as a React Native mobile client with role-based navigation, Rematch and Redux Persist for application state and session persistence, Axios API services for backend communication, Formik and Yup for form handling, and device services for camera and GPS evidence capture.
Key Decisions
- Separated Account Manager and Admin Marketing navigation to keep each role focused.
- Used persisted state so user sessions survive app restarts.
- Kept API integration in service modules to avoid coupling screens directly to endpoints.
- Used form validation for complex activity and task input flows.
- Integrated camera and location only where field evidence is required.
Data Flow
- User login → persisted session → role detection → role-based navigation.
- Account Manager opens activity form → captures location, selfie, environment photo, partner, and description.
- Activity form validation → Axios API service → backend activity endpoint.
- Admin Marketing opens task list → filters by status → views task detail or updates task progress.
- Task create, update, cancel, or activity submission → API response → list/detail refresh.
Flow & Data
State flow and data model
Flow Steps
- User login → persisted session → role detection → role-based navigation.
- Account Manager opens activity form → captures location, selfie, environment photo, partner, and description.
- Activity form validation → Axios API service → backend activity endpoint.
- Admin Marketing opens task list → filters by status → views task detail or updates task progress.
- Task create, update, cancel, or activity submission → API response → list/detail refresh.
Data Model
Entities
- User
- User Role
- Task
- Activity
- Partner
- Project
- Prospect
- Photo Evidence
- Location
Relationships
- User has one User Role
- User can submit many Activities
- Task can reference Project or Prospect data
- Task can have progress and status updates
- Admin Activity can reference a Task
- Activity can include Photo Evidence
- Activity can include Location context
- Activity can reference Partner data
- User Role defines navigation and action access
Business Logic
Rules that drive decisions
- Users are routed to Account Manager or Admin Marketing flows after login.
- Activity submission requires required fields and evidence before it can be sent.
- Camera and location permissions must be available before evidence capture.
- Admin Marketing can create, update, and cancel tasks with the expected task context.
- Task and activity lists must refresh after create, update, or cancel actions.
- Persisted session state keeps the user logged in across app restarts.
Scope & Constraints
Project boundaries
Scope
- Daily activity reporting
- Role-based Account Manager and Admin Marketing workflows
- Task creation, detail, update, and cancellation
- GPS, selfie, and environment photo evidence capture
- Team activity visibility
- Project and prospect based task creation
Constraints
- Camera and location permission handling
- Field network reliability
- Multiple role-specific workflows
- Complex validated forms with image, partner, and task data
- State persistence and list refresh consistency
Your Contribution
What I handled directly
- Built mobile screens for daily activity reporting and admin task management.
- Implemented role-based navigation for Account Manager and Admin Marketing users.
- Integrated backend APIs using Axios for authentication, users, activities, tasks, projects, and prospects.
- Managed application state and persisted sessions with Rematch and Redux Persist.
- Built validated activity and task forms using Formik and Yup.
- Integrated camera and GPS location capture for field activity evidence.
- Created admin flows for task creation, task detail, task cancellation, and task-related activity updates.
- Organized screens, services, store, helpers, and reusable components for maintainability.
Challenges → Solutions
Key problem solving
Challenge
Permission rejection for camera/location
Solution
Added guided permission handling and validation states so users understand why photo or location evidence is required.
Challenge
Incomplete activity submissions
Solution
Used form validation to block submission until required field, partner, image, and location data were complete.
Challenge
Multiple roles with different flows
Solution
Separated account manager and admin navigation so each role only sees the screens and actions relevant to their workflow.
Challenge
Task and activity data needed to stay synchronized after create, update, or cancel actions.
Solution
Refreshed list and detail data after mutations so Admin Marketing and Account Manager screens reflected the latest state.
Trade-offs
Decisions and compromises
- Online-first submission simplified validation and monitoring consistency, but required clear failed-request handling.
- Role-based UI prioritizes clarity over configurability so field users can complete tasks faster.
- Mandatory evidence improves operational trust, but the mobile flow must explain permission requirements clearly.
- Persisted sessions improve usability, but stale sessions need safe API failure handling.
Lessons Learned
What we would repeat
- Permission guidance reduces drop-offs in field workflows.
- Mandatory evidence increases data trust and auditability.
- Role-specific routing prevents operational mistakes.
- Complex mobile business forms need clear validation, not just backend rejection.
- Task and activity workflows are easier to maintain when screens, services, stores, and helpers have clear boundaries.
Edge Cases
Stability in production
- Permission denied (camera/location)
- Incomplete activity data
- Role mismatch for admin actions
- Failed API response during activity submission
- Empty task or activity history
- User returns to a form after interrupted evidence capture
- Task cancellation without a clear reason
- Persisted session becoming stale
Impact
Results and outcomes
Structured field activity
Reporting
GPS + photo evidence
Validation
Admin task visibility
Operations
Gallery
Key screens
Auth Login
Key Takeaways
What mattered most
- Mobile
- Activity
- Task Management
- Field Evidence