How kevinfd95/bibliapp works
Project type and purpose
• Bibliapp is a full-stack, cross-platform mobile application. The frontend is implemented in React Native (Android/iOS) and the backend is a Flask (Python) REST API. Its purpose is to let users organize, search, read and purchase books/ebooks, with features like collections management, advanced search, recommendations, user profiles and PDF/EPUB viewing.
File structure
• Top-level:
• frontend/ → React Native app organized by assets, src (components, views, controllers, api, context, services, styles)
• backend/ → Flask project with MVC folders: controllers, models, services, routes, validations, database connection, migrations, commands, feeders, tests
• database/ → raw SQL schema
• MVC pattern in the backend:
• routes → HTTP endpoints
• controllers → business logic entry points
• services → reusable logic (API responses, file converters, notifications)
• models → ORM/mapping objects
• database → connection & query utilities
• feeders & migrations → schema evolution & seeding
• Configuration/build: requirements.txt, package.json, migration scripts, secret key generator, test fixtures.
README for additional insights
• Confirms MVC pattern, tech stack (React Native, Flask, MySQL), JWT for auth, encryption via Bcrypt/SSL, integration points (Firebase/AWS S3 for storage).
• Outlines key modules: collection management, search/filters, recommendation engine, user management, ebook viewer.
Additional advice
• Every major folder as a component (e.g., converters, notifications, validations).
• Cross-cutting middleware (JWT/token_required) as an overlay or distinct path through the request flow.
• Migration & feeder tools as part of the deployment/process pipeline off to one side.
• Keep it high-level enough to fit on a single slide but detailed in showing each layer of the MVC chain and external integrations.