01 / The problem
Sensitive organizational work needed secure, structured workflows.
The organization needed a more reliable way to manage pastoral and remittance-related work. The platform had to keep authenticated areas protected, apply permissions consistently, and support core workflows without exposing sensitive information.
02 / My role
Leading architecture and delivery across the full stack.
I led full-stack development across architecture, authentication, protected routes, permission handling, workflow development, and production deployment. I also coordinated with UI/UX and backend support so implementation decisions remained aligned across the team.
03 / What I built
Core contributions
- Led the application architecture and full-stack implementation approach
- Designed the authentication flow and protected-route behavior
- Implemented permission-aware access for sensitive workflows
- Developed core pastoral and remittance management workflows
- Coordinated implementation across UI/UX and backend support
- Prepared and supported the production deployment on AWS infrastructure
04 / Technical decisions
Protecting access at each layer
Authentication before workflow access
Reason: Sensitive pastoral and remittance areas could not rely on navigation visibility alone.
Result: Protected routes made authentication a prerequisite for reaching internal workflows.
Permission-aware operations
Reason: Authenticated users still require different levels of access based on responsibility.
Result: Permission handling became part of the workflow design and Directus-backed data access.
Separated application and file hosting
Reason: Application deployment and stored assets have different operational needs.
Result: AWS Lightsail supported the deployed application while Amazon S3 handled object storage responsibilities.
05 / Challenge
Coordinating secure workflows without exposing private details.
The main challenge was aligning authentication, permissions, workflow behavior, and deployment while coordinating across contributors. Security decisions needed to remain consistent without making the system difficult for its intended users.
06 / Outcome
A deployed foundation for protected organizational workflows.
The project established an authenticated, permission-aware application structure for pastoral and remittance management, supported by coordinated full-stack implementation and production deployment.
07 / Skills demonstrated
Capabilities used
- Full-Stack Leadership
- Authentication
- Protected Routes
- Permissions
- Directus
- Expo
- Node.js
- AWS Deployment