Controller Β· Next.js
Layer responsible for routes, REST APIs, and the admin dashboard.
A platform to track completed, in-progress, and planned reading, with detailed control over a personal library.
ReadMonitor centralises book tracking with a focus on quick lookups and detailed cataloguing.
Each component owns specific responsibilities, enabling independent testing and incremental evolution.
Layer responsible for routes, REST APIs, and the admin dashboard.
Orchestrates persistence in SQLite and the business rules layer.
Mobile interface to add, browse, and update books quickly.
The structure reinforces layer separation and simplifies independent deployments.
ReadMonitor/
βββ Controller/ # Next.js for routes/admin
βββ Model/ # Node.js + Sequelize + SQLite
βββ View/ # Mobile app via Expo
βββ db.sqlite3 # Local database
βββ README.md # Full documentation
Prepare each module in its corresponding directory, ensuring environment variables and dependencies are correct.
git clone https://github.com/eduardo45MP/ReadMonitor.git
cd ReadMonitor
cd Controller
npm install
npm run dev # Default port 3000
cd ..
cd Model
npm install
npm start # Starts API + SQLite
cd ..
cd View
npm install
npm start # Open the Expo app on your device
cd ..
Align each layer configuration to the same database/endpoint. Consider seed scripts to populate initial data.
There is room for new features, integrations, and UX improvements across the web panel and the mobile app.
Dashboards with reading time, favourite genres, and milestone tracking.
Integrations with cloud services and automated library exports.
Optimised flows for adding books with barcode scan or cover capture.
Review portfolio/docs/ROADMAP.md to align priorities and keep visual consistency with the guide in portfolio/docs/visualID.md.