Repore
Web product, mobile app, and the API behind both
A Prompt Computers product. I built the web version and kept the API and cloud.
Problem
Prompt Computers needed Repore on the web and on mobile, with one API and a deployment the team could operate after the first version.
Solution
The API behind the product handles accounts, roles, content, uploads, and Stripe purchases. It deploys as an ECS service. Files go to S3. Email is queued on SQS and sent with SES. Mobile push uses an SNS platform application.
What I handled
I built the first web version myself. I led the team that built the mobile app. I maintained the API and the cloud infrastructure.
Architecture & Technical Decisions
The Repore API is an Express service on ECS, backed by MongoDB. The deployment task is the repore-staging service. I am not describing WebSockets or an external identity provider here, because this API does not show them.
- Architecture pattern
- Express API with role-based authentication
- Hosting & deployment
- AWS ECS, with the container image in ECR
- Data layer
- MongoDB
- Integrations & services
- S3, SQS, SES, SNS platform application, Stripe
Talk about a system like this
The write-up above is the record. If you want a system like it, send a note.