How yashendra767/pulsesync works
Project type and purpose
• From the file tree and README, PulseSync is a full-stack Android hospital management application.
• It consists of an Android (Kotlin) client (“app/” directory) and a Firebase-based backend (Firestore, Authentication, Cloud Functions in “functions/”).
• Its purpose is to support four user roles (Admin, Doctor, Nurse, Pharmacist) for admissions, bed management, inventory, dispensing, reporting, and notifications.
File structure
• Top-level:
• app/ – Android Studio project (Gradle, Kotlin sources, resources, layouts, navigation graph, tests, google-services.json)
• functions/ – Node.js Cloud Functions for notifications or business-logic hooks
• firebase.json/.firebaserc – Firebase CLI config
• build scripts and Gradle settings
• app/src/main/java/com/example/pulsesync – separated by feature and by user role packages (beds/, doctor/, nurse/, pharmacist/, reports/, user_manage/) indicating a modular, MVVM-style layering in code.
• app/src/main/res – Material Design layouts, drawables, menus, navigation graph.
• Presence of MyFirebaseMessagingService.kt for FCM and various adapters for lists.
README for additional insights
• Firebase collections: users, beds, admissions, inventory, tasks, alerts, dispensing_history, doctors, reports
• Uses Firebase Auth, Firestore, planned Cloud Functions for notifications, plus third-party libs (MPAndroidChart, ZXing, Glide, Cloudinary, OkHTTP3).
• Architecture stated as “Modular architecture with separate Activities and Fragments per user role” and “MVVM architecture (partially implemented).”