Project Report

Overall Status:

• Clear Communication and early progress on designs.

Planned:

Complete basic wireframes

Actual:

• Conducted requirements call and clarification session with the client
• Created a detailed questionnaire
• Started working on wireframes in Figma

Dependencies:

• None

Overall Status:

• Significant progress in technical planning.
• Good Momentum but impacted slightly by external delays.

Planned:

Develop Data Flow Diagrams (DFD), Identify AWS services

Actual:

• Showcased wireframes for Customer, Bike Provider, and Battery Provider apps
• Sent Customer app designs to the client for approval
• Conducted scope realignment analysis and documented findings
• Developed first-level data flow diagram
• Held internal discussions on the initial database schema

Dependencies:

• Awaiting confirmation on wireframes before proceeding to the next stage
• Progress is temporarily on hold pending the outcome of the scope realignment analysis

Overall Status:

• Scope has mostly stabilized.
• Alignment improving, moving closer to development readiness.

Planned:

Finalize project scope for bike provider app and freeze functionality across all its roles

Actual:

• Received PRD, product flow, and workflow diagrams for the Bike Provider app
• Conducted team discussions and prepared a questionnaire
• Finalized scope for the Bike Provider app
• Started database schema design

Dependencies:

• The client has indicated that the Battery Provider requirements are expected to be shared by the weekend

Overall Status:

• Foundation phase is nearly complete: Requirements, scope (Bike Provider App), user stories, schema, and SRS are all in place.
• Technical groundwork such as AWS service planning and architecture has begun.

Planned:

Database architecture completion

Actual:

• Finalized the complete DB schema for the Bike Provider app internally and shared it with the Nura team
• Documented user stories and tasks in JIRA with subtasks
• Completed the SRS document and module-wise data flow
• Conducted AWS services research
• Identified system architecture and technology stack

Dependencies:

• Battery Provider App requirements are expected but have not yet been received.
• Awaiting branding details (fonts, colors, logo) to proceed with visual theming.
• Access to AWS credentials is awaited to proceed with Development setup.
• Aggregator App requirements are expected but have not yet been received.
• The Ops panel requirements related to the Battery Provider App, Aggregator App, and Customer App need to be fully defined.
• Database schema confirmation is pending to finalize backend structuring.
• Confirmation on the Bike Provider App SRS document is awaited.

Overall Status:

• Progress has moved into the development phase with key APIs in progress.
• Frontend designs underway for both mobile and web applications.

Planned:

Set up cross-platform mobile app structure and base navigation

Actual:

• Developed APIs for 3 epics: Login, Roster, and Shift Login
• Finalized the schema and initiated DB creation
• Started Figma design for the Bike Provider App
• Presented initial Figma designs and received feedback
• Finalized backend architecture (mono-modular microservices approach)
• Initiated frontend design work for the Ops Panel

Dependencies:

• Battery Provider App requirements are awaited (From week 3)
• Branding guidelines are still pending (From week 3)
• AWS credentials are required for setting up the development environment
• Aggregator App requirements have not yet been received
• Ops Panel requirements (Battery Provider, Aggregator, and Customer Apps) are pending finalization
• Confirmation on the Bike Provider App SRS document is awaited

Overall Status:

• Back-end development continues with the expansion of API coverage and setup of unit tests.
• Flutter development environment and infrastructure are being prepared.

Planned:

Implement secure OTP login and KYC upload flow

Actual:

• Developed APIs for roles, skills, vendors, and warehouses
• Developed Leave & Attendance Management and Learning Module APIs
• Presented Ops Panel designs to the Nura team
• Created required DB tables for upcoming APIs
• Planned Flutter architecture and environment setup
• Initiated unit test case creation for developed APIs

Dependencies:

• Battery Provider App requirements are awaited (From week 3)
• Branding details are still pending (From week 3)
• AWS credentials are needed to proceed with development setup
• Aggregator App requirements have not yet been received
• Ops Panel requirements (Battery Provider, Aggregator, and Customer Apps) are pending finalization
• Confirmation on the Bike Provider App SRS document is awaited (From week 5)

Overall Status:

• Key milestones include UI finalization for the mechanic role, initiation of Flutter development.
• Receipt of Battery Provider App requirements marks significant progress.

Planned:

Develop ride booking, QR-based control, and real-time vehicle tracking

Actual:

• Finalized Figma designs for the mechanic role in collaboration with the Nura team
• Received PRD for the Battery Provider App
• Initiated Flutter development focusing on the performance module
• Developed APIs related to zone and task management
• Finalized backend Ops Panel design

Dependencies:

• Branding details are still awaited (From week 3)
• Aggregator App requirements have not yet been received
• Detailed Ops Panel requirements for Aggregator and Customer Apps are pending
• Confirmation on the Bike Provider App SRS document is awaited (From week 5)

Overall Status:

• Week 8 saw steady progress across backend deployment, authentication workflows, and frontend development.
• Key modules were implemented to support initial integration and testing, with foundational components now in place.

Planned:

Deploy backend application to staging environment (EC2), Complete development of Admin & Mobile User Authentication modules, Begin Flutter integration for Auth and Task modules, Finalize Inventory Incharge UI design in Figma, Continue building the Ops Panel with Auth features and role-based routing

Actual:

• Deployed backend to EC2 for testing and integration
• Completed Admin Auth APIs: Create Admin, Login, OTP verification, Password reset, and Bike Provider User creation
• Delivered full Mobile User Auth flow: Login via phone, OTP handling, token refresh/validation, logout, and contact support
• Developed and integrated the complete Flutter UI for the authentication module, covering user onboarding, OTP flows, and session management
• Successfully connected the Auth module to backend APIs for real-time validation and token handling
• Initiated development of Task and Performance modules tailored for the Bike Provider App (Mechanic role)
• Finalized Inventory Incharge UI in Figma
• Set up scalable Next.js architecture for the Ops Panel; implemented full Auth workflow with role-based access control and route guards

Dependencies:

• Awaiting branding assets (fonts, colors, logo) for visual theming
• Detailed requirements for Ops Panel (Aggregator & Customer Apps) are yet to be finalized
• Confirmation on the Bike Provider App SRS document is awaited

Overall Status:

• Work progressed steadily on backend deployment, CI/CD setup, and overall development.
• Key features like Task, Contact Support, and Shift Management moved forward.
• The mobile app now supports persistent login, offline access, and better user feedback.
• Core designs and APIs for different user roles are now ready.

Planned:

Finalize and test CI/CD pipeline, Complete API integration for shift assignment, Continue Task API development and begin test workflows, Implement lookup APIs for consistent data mapping, Expand Contact Support with ticketing/escalation logic, Enhance Flutter offline support and caching strategies, Integrate Task and Performance UI for Bike Provider app, Build remaining Inventory features

Actual:

• Set up subdomain, SSL, and resolved HTTP/HTTPS issues
• Fixed API bugs and resolved Swagger documentation on EC2
• Initiated and configured CI/CD pipeline
• Developed Task and Lookup Category APIs
• Implemented Contact Support APIs
• Ops-Shift creation: UI and API completed
• Ops-Shift assignment: UI completed (API pending)
• User management: UI & API for Warehouse Incharge role
• Master Operations (Super Admin): UI for Skills, Vendors, Zones, Warehouses, Roles, Spare Parts
• Roles & Skills: API integrated
• Fully integrated UI & API for Leave, Roster, Help/Support, Learning, and Edit Profile modules
• Presented design demo for Battery Provider app
• Finalized Inventory Incharge UI in Figma
• Login module handles persistent sessions and logout
• Offline login state handling implemented
• Contact Support screen created and integrated
• Waiting screen added to guide users post-support request based on role/profile

Role Changes:

• A new role, Sales Executive, has been added
• The roles of Bike Mover and Battery Mover have been moved to the Connector App

Dependencies:

• Awaiting branding assets (fonts, colors, logo) for visual theming
• Confirmation on the Bike Provider App SRS document is awaited

Overall Status:

• Week 10 saw major progress in backend APIs and frontend integration across Task, Roster, Learning, Attendance, and Leave Management modules.
• Significant advancements were made for Warehouse Incharge and Mechanic roles, with continued improvements to user support and geofencing.

Planned:

Implement completed task APIs, finalize spare part database integration, continue enhancements in roster module and geofencing, integrate Attendance & Leave modules for field roles, complete UI/API for Support module, showcase Warehouse Incharge wireframes for review

Actual:

• Implemented 'Get All Completed Tasks by User ID' API
• Fixed date-related issue and completed bug fixes in the Roster module
• Added spare part CRUD operations in Task module
• Created database tables and developed spare management APIs
• Delivered CRUD APIs for FAQ and Raise an Issue modules
• Implemented check-in/check-out APIs with geofencing verification
• Developed and integrated Learning module and Leave Management APIs
• Showcased wireframe demo for Warehouse Incharge role
• Added 'Request Battery' and 'Request Pickup Battery' features in Battery module
• Integrated APIs for Today’s Shift, Roster Module, and Shift Template
• Completed API/UI integration for User Management and Daily Attendance
• Integrated and displayed all Leave Requests in table view
• Built Home Screen UI for Bike Provider App
• Integrated Geo-fence and On Duty API logic (working on edge case testing)
• Developed Task UI for Mechanic role as per defined flow
• Integrated Edit Profile API and UI
• Delivered UI/API for Roster History screen and custom Calendar component
• Integrated FAQ & Raise Concern APIs with UI
• Completed Logout flow integration

Dependencies:

• Awaiting branding assets (fonts, colors, logo) for visual theming
• Confirmation on the Bike Provider App SRS document is awaited

Overall Status:

• Consistent backend API development and frontend integration continue across the Inventory, Task, Roster, Learning, and Ops modules.
• Steady progress on geofencing features and support workflows.

Planned:

Complete remaining Task APIs, Continue roster/geofencing enhancements, Advance Ops panel design and UI integrations, Complete bike provider app UI development

Actual:

• Fixed profile screen issues; added snackbar on Performance Not Ready screen
• Built UIs: Inventory Activities, Raise Ticket (with API), Transfer Inventory, Raise a Concern
• Delivered UIs: On-duty Shift, Tea & Lunch Break, Mechanic Task, Confirmed Issue, Task Work
• Implemented Spare Collection flows, including QR
• Completed Learning Modules master UI
• Integrated APIs for Roles, Skills, Vendor, Warehouse masters
• Added map with current location picker for warehouse creation
• Redesigned header to side navbar; completed Role Permission Management UI
• Implemented roster validations for check-in/check-out
• Developed geofencing logic
• Progressed Task Screen APIs: Request Task, Accept Task, Verify Bike, Create Issue, Get Task Issues by Task Detail ID, Add Spare to Issue, Get Added Spares for Task Detail ID

Dependencies:

• Awaiting branding assets (fonts, colors, logo) for visual theming
• Confirmation on the Bike Provider App SRS document is awaited

Overall Status:

• Wireframes for key roles (Warehouse Incharge, Battery Manager, Central Ops Executive web & mobile) have been completed. UI development is underway for Inventory Incharge, Warehouse Incharge, and Mechanic Task, with API integration initiated for Inventory Incharge.

Planned:

Progress Continue task API development ,Advance Inventory Incharge module with full API integration,Expand Warehouse Incharge UI development,Complete Mechanic Task UI and finalize database tables

Actual:

• Completed wireframe for Warehouse Incharge web app (Bike, Battery, Roster, Leave Management, User Management, Inventory)
• Completed wireframe for Battery Manager web app (Battery, Charging Units, Roster
• Completed wireframe for Central Ops Executive web app (Bike, Battery, User List, Bike Onboarding)
• Completed wireframe for Central Ops Executive mobile app
• Started Customer App wireframe
• Inventory Incharge UI completed; API integration started
• Warehouse Incharge UI started
• Mechanic Task UI initiated
• Database tables discussion completed
• Partially completed Customer App database
• Partially completed Task API

Dependencies:

• Awaiting branding assets (fonts, colors, logo) for visual theming

Overall Status:

• UI development progressing strongly with multiple modules completed. Initial API integration initiated.

Planned:

• Continue UI development for major modules
• Begin integration for inventory APIs

Actual:

• Completed UI screens:
• - Bike List
• - Bike Registration
• - Bike Operations (deployment, history, pickup request)
• - Fleet Management (create fleet, map to vendor, map to bike, map to zone)
• - User Onboarding
• - Batteries Dashboard
• - Charging Machines
• Completed Inventory Incharge API integration

Dependencies:

• Awaiting branding assets (fonts, colors, logo) for visual theming

Overall Status:

• Progress tracking formalized; work initiated on Battery Provider UI.

Planned:

• Create progress tracking mechanism
• Begin Battery Provider UI

Actual:

• Progress sheet created
• Battery Provider UI started

Dependencies:

• IoT test server setup completed; awaiting sample data, topics (endpoints), and full flow
• Awaiting branding assets (fonts, colors, logo) for visual theming
• Bike Provider App additional tables

Overall Status:

• Major progress on Bike Provider and Battery Provider apps; API integration advancing. Updates to scope incorporated.

Planned:

• Build Bike Provider and Battery Provider app screens
• Complete API flows for Bike Provider
• Incorporate updated scope changes

Actual:

• Worked on Bike Provider and Battery Provider apps
• Presented demo of app screens to Nura team
• Received updated screen list & revised flow; changes underway
• Completed Bike Provider flow APIs with state validation
• Finalized Bike Provider full integration
• Completed Battery Provider UI
• Held detailed tables discussion for entire app

Dependencies:

• Payment gateway confirmation pending
• Connect App tables
• Customer App tables

Overall Status:

• Substantial progress in role-based UIs. Customer and Connect apps development initiated.

Planned:

• Complete Warehouse Incharge UI screens
• Develop Battery Incharge role screens
• Advance Customer and Connect apps

Actual:

• Completed Warehouse Incharge UI screens and demo
• Completed UI for: Bike Info, Bike Registration, Bike Operations, Fleet Management, Battery Info, Battery Operations, Roster Management, Leave Management, Master Operations (Skills, Role, Contract, Vendor, Warehouse)
• Completed UI for Battery Incharge role (Battery Info, Registration, Operations)
• Customer App UI development started
• Customer App Auth API completed
• Connect App UI completed
• Conducted app-wide tables discussion
• Connect App API integration for bike mover completed

Dependencies:

• Payment Gateway confirmation pending

Overall Status:

• Central Ops UI delivered; major progress in APIs including IoT setup.

Planned:

• Deliver Central Ops UI
• Advance API integrations across Customer and Connect apps
• Deploy Battery Incharge app

Actual:

• Completed first-level UI screens for Central Ops Executive role
• Completed modules: Bike Info, Bike Registration, Bike Operations, Fleet Management, Battery Info, Battery Operations, Roster, Leave Management, Master Operations (Skills, Role, Contract, Vendor, Warehouse)
• Completed and deployed Battery Incharge module; shared app link with Nura team
• Customer Auth APIs completed
• Connect App flow APIs completed
• Started Customer App flow API development
• IoT server setup using Mosquito broker
• Conducted further tables discussion for app
• Connect App API integration for bike mover completed

Dependencies:

• Payment Gateway confirmation pending
• IoT: Sample data, topics, full flow pending
• Bike controls & real-time data pending
• Protocol confirmation pending
• IoT DB + InfluxDB pricing confirmation pending
• IoT broker decision pending (AWS IoT Core / Custom Server)
• Battery tables & IoT integration pending
• Battery Mover scanner flow not finalized

Overall Status:

• Customer App backend integration initiated with login, bike selection, and pricing modules.

Planned:

• Begin Customer App API integration
• Develop bike selection and pricing flows

Actual:

• Customer App API integration for login completed
• Bike selection APIs integrated
• Price summary page API integration completed

Dependencies:

• Payment Gateway confirmation pending
• IoT: Sample data, topics, full flow pending
• Bike controls & real-time data pending
• Protocol confirmation pending
• IoT DB + InfluxDB pricing confirmation pending
• IoT broker decision pending (AWS IoT Core / Custom Server)
• Battery tables & IoT integration pending
• Battery Mover scanner flow not finalized

Overall Status:

• Customer App backend integration advanced with completion of pricing, wallet, FAQ, and profile modules.

Planned:

Continue backend API integration for pricing plans, wallet functionality, and user profile management

Actual:

• Pricing plan page API integration completed
• FAQ API integrated
• Wallet module fully integrated (Add Money, Pay SD Money, View Transaction & Refund History)
• Profile data update API integration completed

Dependencies:

• Payment Gateway confirmation pending
• IoT: Sample data, topics, full flow pending
• Bike controls & real-time data pending
• Protocol confirmation pending
• IoT DB + InfluxDB pricing confirmation pending
• IoT Integration (device + broker)
• IoT Database
• Decoding Logic
• Google Maps API

Overall Status:

• Customer App integration expanded with station and ride-related APIs, enhancing in-app visibility and purchase flow.

Planned:

Integrate APIs to display bike stations, battery stations, and warehouses. Finalize ride history and plan purchase API flows

Actual:

• Bike station display with API integration completed
• Battery station display with API integration completed
• Warehouse display with API integration completed
• Ride history API integration completed
• Buy a Plan full flow integration completed (Buy using Wallet and Payment Gateway)

Dependencies:

• Payment Gateway confirmation pending
• IoT: Sample data, topics, full flow pending
• Bike controls & real-time data pending
• Protocol confirmation pending
• IoT DB + InfluxDB pricing confirmation pending
• IoT Integration (device + broker)
• IoT Database
• Decoding Logic
• Google Maps API

Overall Status:

• Work focused on starting core token flows, UI setup, and foundational backend structures. IoT and payment integrations could not progress due to dependencies.

Planned:

• Start basic implementation of bike token booking APIs
• Set up initial structures for token details and token history
• Prepare UI for token booking and success screens
• Begin preliminary setup for in-app navigation using mock data
• Coordinate with client and IoT vendor to clarify required dependencies

Actual:

• Completed API integration for bookTokenForBike
• Initiated implementation of in-app navigation structure (using development keys)
• Added UI for Token Booked Successfully
• Loaded and tested bike station list using existing static/mock data
• Conducted discussion calls about project dependencies and upcoming integrations
• Performed outdoor testing using mock navigation data to validate UI/UX flow

Dependencies:

• Google Maps API Key
• IoT Time-Series Database

Overall Status:

• Progress increased with broader API development, customer-app enhancements, and structural work on token and plan modules. IoT and Razorpay-related tasks remained blocked, but all non-dependent backend, UI, and provider-side structures advanced steadily.

Planned:

• Expand customer-app API development (token details, plan, center, station data)
• Improve token history and booking UI flows
• Enhance center/station mapping using static data
• Continue coordination with client to obtain pending IoT and Razorpay inputs

Actual:

• Implemented several Customer App APIs : getTokenDetails, getTokenHistoryByUserId, getBookedCenterByUserId, nearbyCentersByBatteryTypeForBikeType (using existing center data), getActivePlanForCustomer , getBikeTypesAvailabilityByCenterId
• Expanded Module (partial, mocked DB responses): getActiveTokensForBikeAttach
• Added customer-side module logic: getTokenList, getTokenDetails
• Improved in-app navigation transitions and UI for booked tokens
• Updated mapping logic for bike/battery stations (using mock/static data)
• Conducted additional testing for booking and navigation flows
• Continued coordination with client and IoT vendor on dependency fulfillment

Dependencies:

• Google Maps API Key
• IoT Time-Series Database

Overall Status:

• Significant progress was made across customer app modules, token flows, IoT data handling, pricing logic, and operational dashboards. Real-time bike tracking and charger-based booking/check-in were successfully completed. Backend, frontend, and infra tasks all advanced, supported by active coordination with the IoT vendor.

Planned:

• Validate token booking/attach flows and implement scan/attach APIs
• Add token expiry, UI updates, and build token history
• Improve charging station visibility and pricing summaries
• Set up Mosquitto, start IoT ingestion, and test decoding logic
• Enhance mapping APIs, continue Razorpay setup, and improve deployments

Actual:

• Completed token booking, scan/attach APIs, expiry logic, and history screen
• Refined station visibility, updated all pricing and plan APIs
• Set up Mosquitto, received IoT data, stored packets, and completed decoding + real-time tracking
• Implemented bike ON/OFF command and charger-based token flows
• Updated multiple customer/charger APIs, fixed vendor issues, and resolved EC2 deployment
• Reviewed DB & AWS infra, created new APIs, and completed vendor registration + bike ops module
• Delivered full demo: vendor login, bike registration, IoT tracking, deployments & operations

Dependencies:

• Google Maps API Key

Overall Status:

• Advanced integration phase completed with payment systems fully functional.
• All core platforms (Customer, Bike Provider, Battery Provider, Ops) approaching completion.
• UAT backend migration successful with comprehensive testing.

Planned:

Finalize token booking flows with payment integration, Complete battery provider app with Razorpay, Migrate and test all modules in UAT backend environment

Actual:

• Token booking flows finalized with Razorpay integration and multiple state validations
• Battery provider app fully operational with payment gateway integration
• Customer app APIs and UI advanced significantly
• All modules tested and refined in UAT environment
• Performance optimizations applied across all platforms
• Multiple backend API fixes completed

Dependencies:

• Google Maps API Key

Overall Status:

• Significant progress was achieved across app testing, token flows, battery provider flows, roster/leave modules, map features, and full UAT backend migration.
• Multiple modules reached developer-complete status with substantial UI/UX and performance improvements.

Planned:

• Continue end-to-end testing and bug logging
• Extend-plan flow integration
• Improve token and battery provider flows
• Advance UAT backend setup, SSL configuration, and DB migrations
• Complete roster, leave, spare parts, mechanic, inventory, and mover module migrations
• Implement location permissions, map enhancements, CRUD modules, and role-permission updates

Actual:

• Application-wide testing initiated; bug sheet created
• Extend-plan completed (UI + API), wallet enhancements, Razorpay trigger, and in-app notifications implemented
• Location access logic, camera permissions, QR scanning (bike + charger), and route optimization improved
• Token flows refined for both charger and bike; full flow fixed and tested in battery provider app
• Major UI refactors: Swap Battery, LeaveHistory, TokensCard, roster UI, EditProfile, and multiple screen optimizations
• Battery provider, OPS, customer, mover, mechanic, and inventory flows tested and refined
• CentralOps, provider, and bike-mover flows optimized (task accept/start/status, validations, skip logic)
• CRUD completed for Battery Types, Battery Registration, Bike Types Master, and Access Layer UI
• Role-permission mappings updated, filters cleaned, pagination added, dynamic plan_type_id fixed
• Map module enhanced with shape drawing (rectangle/circle/polygon) and integrated with center creation
• Full UAT environment set up (EC2, PM2, Prisma fixes, domain + Nginx, DB restore, sample data)
• Roster, Leave, Spare Parts, Mechanic, Inventory Incharge, and Mover modules migrated from warehouseId → centerId and fully tested
• Multiple backend API fixes across Today's Shift, roster duplicates, missing IDs, data mismatches, and auth errors

Dependencies:

• Google Maps API Key

Overall Status:

• Substantial progress was made across backend migration, OPS testing, vendor-side fixes, and deployment tasks.
• SMS functionality and notification module were successfully implemented, and CI/CD setup was completed. Multiple modules underwent testing with significant bug fixes.

Planned:

• Complete database migrations (Warehouse → Centers, Branch)
• Deploy backend application using the new database
• Fix OPS panel bugs and continue testing
• Implement SMS logic and notification module
• Support frontend deployment and CI/CD setup

Actual:

• Migrated Warehouse to Centers table and Branch data
• Deployed backend application using the new database
• Resolved Prisma issues
• Implemented charger on/off status functionality
• Fixed OTP verification bug in OPS
• Migrated Pages and Role-Permission data for OPS panel testing
• Fixed bugs in Customer and Battery Provider applications
• Implemented SMS functionality and verified SMS sending via Customer Login API
• Performed OPS application testing and fixed multiple bugs
• Resolved vendor-side login issues in OPS panel
• Added new API endpoints: getUsersByVendorId, getCentersByVendorId, getDailyAttendance, getLeaveRequestByVendorIdAndCenterId, getShiftTemplateByVendorIdAndCenterId, getRostersByCenterIdAndVendorId, getUsersByCenterId
• Fixed getCenterByVendorId ID issue, time formatting issues in shift template APIs, null-to-empty-array issue in getShiftTemplateByVendorIdAndCenterId
• Deployed frontend application
• Resolved deployment issues and configured Nginx + PM2
• Set up CI/CD pipeline, debugged and completed implementation
• Continued OPS panel testing
• Implemented Notification module using Firebase
• Created sample test endpoint and verified push notifications
• Tested vendor login modules (bikes, users, roster, attendance, fleet) and fixed bugs
• Tested 80% of central ops executive modules and fixed bugs
• Tested 40% of warehouse incharge modules and fixed bugs

Dependencies:

• Google Maps API Key

Overall Status:

• Strong progress across core backend modules and mobile app with successful Group Plans and Fleet upgrades, major API refactoring, cron and token logic improvements, and extensive UAT testing with the Nura team.
• Multiple critical workflows are now stabilized and production-ready.

Planned:

• Enhance and refactor core modules (User, Plan, Fleet, Vendor, Center, Customer)
• Improve API consistency and data handling
• Add new business workflow endpoints
• Support Nura UAT testing and resolve high-priority issues
• Strengthen cron services, bike state, and token/lease logic

Actual:

• Shared APKs for all apps and the Web Ops panel for UAT
• Completed Group Plan & Asset Group Mapping UI + API integration
• Updated Fleet module with Active/Inactive toggle and flow enhancements
• Fixed role-based user creation issues
• Added state/city to Vendor, improved Center capacity & bike–battery mapping
• Fixed Customer Support stats APIs
• Implemented and tested Group Plan & Fleet APIs
• Migrated vendor mapping from warehouse to center
• Improved leave, deploy, and token workflows with better filtering and expiry logic
• Implemented plan cancellation with refund processing
• Integrated and optimized cron services & charger status tracking
• Improved bike detachment, lease handling, and token booking
• Enhanced User, Plan, Auth, and Center services with validation and response cleanup
• Added file upload for customer issues & category lookup API
• Added centre lookup by bike type endpoint
• Completed extensive UAT with Nura team, deployed multiple fixes
• Successfully tested real-time bike ON/OFF flow
• Refactored mobile navigation, added haptics
• Integrated Firebase Analytics, Crashlytics & Performance Monitoring
• Push notification implemented

Dependencies:

Overall Status:

• Successfully Completed — Major enhancements, bug fixes, module restructuring, and multi-application testing were completed as planned. All critical issues were resolved, new modules were integrated smoothly, and the Central Ops Executive workflows were validated through demos. The week progressed without any blockers, ensuring stable and improved system performance across apps.

Planned:

• Fix issues in bike types and battery types.
• Create a new screen for Customer Management and complete API integration.
• Separate User Management into Admin Management and Employee Management and integrate APIs.
• Resolve all bugs related to the Central Ops Executive role in the web apps.
• Prepare for demo and discussion with Sravan.
• Support Notification module testing across all apps.
• Test Bike Provider, Battery Provider, and Customer apps and fix reported bugs.

Actual:

• Fixed issues in bike types and battery types.
• Developed a new Customer Management screen and completed API integration.
• Separated User Management into Admin Management and Employee Management, with full API integration for both modules.
• Completed all bug fixes related to the Central Ops Executive role across the web apps.
• Conducted a demo of the Central Ops Executive role for Sravan, covering workflows and validations.
• Worked on the Notification module, including demos, validations, and testing across all related applications.
• Performed detailed testing on Bike Provider, Battery Provider, and Customer apps, addressing and resolving all identified bugs.

Dependencies:

Overall Status:

• Successfully progressed through end-to-end testing across all applications with consolidated bug lists received for final resolution.
• Cross-application demos were conducted with the team, covering complete workflows and functionality explanations.
• Identified issues were addressed and fixed in parallel, ensuring continuous progress toward closure with the project now in the final stage of product closure.

Planned:

• Complete testing across all applications
• Review and consolidate bug lists received from testing
• Conduct demos covering all applications and workflows
• Fix identified bugs in parallel during testing
• Focus on resolving major and critical bugs
• Move toward final product closure

Actual:

• Completed comprehensive testing across all applications
• Received and reviewed consolidated bug lists for further action
• Conducted detailed demos with the team, explaining workflows and functionalities of all applications
• Identified bugs during demos and testing and fixed them in parallel
• Focused primarily on resolving major and critical bugs across the system
• Progressed to the final stage of product closure with improved system stability

Dependencies: