14 Oct
|
Shivit Technologies
|
Noida
14 Oct
Shivit Technologies
Noida
1. About Shivit Technologies
Shivit Technologies Pvt. Ltd. develops Shivaizer ERP, a configurable ERP platform built for manufacturing, trading, distribution and other industries. Shivaizer's existing technology stack includes Java Spring Boot, Angular, MySQL and Redis. The platform includes Sales, Procurement, Inventory, WMS, Manufacturing, CRM, Accounts, HR, Quality Management, workflow approvals, dynamic forms, dashboards and reports.
We are looking for an experienced Flutter Mobile App Developer to develop the first phase of Shivaizer's mobile application for Android and iOS using a single cross-platform codebase.
1. Project Objective
The objective is to develop a secure, scalable and user-friendly mobile companion for Shivaizer ERP, enabling authorized users to:
- Log in securely to Shivaizer ERP.
- View role-appropriate dashboards and KPIs.
- Access ERP reports optimized for mobile devices.
- Receive approval notifications, reminders and system alerts.
- View notification details and navigate to the relevant ERP screen where supported.
- Monitor important business information while away from their desktop.
Phase 1 will focus on information access and notifications, not full transaction processing. Module-wise transaction viewing, editing, updating and operational workflows will be introduced progressively in Phase 2 and subsequent releases.
1. Scope of Work — Phase 1A. Login and Authentication
- Secure login and logout.
- Forgot password/password reset, subject to existing backend support.
- Company/tenant selection, where applicable.
- Role-based access.
- Secure session and token management.
- Biometric authentication, where appropriate and compatible with the existing authentication architecture.
- Session expiry and secure re-authentication.
B. Mobile Dashboard Develop a responsive mobile dashboard displaying KPIs and business summaries based on the logged-in user's permissions.
Potential dashboard categories include
- Management dashboard.
- Sales dashboard.
- Purchase dashboard.
- Inventory dashboard.
- Production dashboard.
- Finance dashboard.
- Other existing Shivaizer dashboards, subject to API and mobile usability readiness.
Required capabilities:
- KPI cards and summary metrics.
- Charts and graphs.
- Date-range filters.
- Applicable company and business-unit filters.
- Drill-down navigation to supported reports.
- Refresh and data-loading indicators.
- Access controlled by existing roles and permissions.
The application should reuse existing dashboard data sources and business logic wherever practical rather than duplicating calculations in the mobile app. C. Reports
Enable users to access selected existing Shivaizer reports in a mobile-friendly format.
Required capabilities
- Report listing based on user permissions.
- Search and categorization of available reports.
- Report filters and parameters, where supported.
- Mobile-friendly tables, summaries and charts.
- Sorting and pagination where applicable.
- Date-range selection.
- Refresh and loading/error states.
- Export or sharing of reports where supported by existing APIs and permissions.
The architecture must accommodate the future addition of reports without requiring a separate application release for every report, wherever configuration-driven delivery is feasible. The exact Phase 1 report catalogue will be finalized jointly with the Shivaizer team before development begins.
D. Notifications and Alerts
Implement a centralized notification experience covering:
- Approval notifications.
- Reminders.
- ERP system notifications.
- Transaction status updates.
- Scheduled notifications.
- Other supported alerts generated by Shivaizer.
Required capabilities:
- Push notifications on Android and iOS.
- In-app notification center.
- Read/unread status.
- Notification history.
- Notification timestamps and relevant references.
- Deep linking to the relevant ERP screen or transaction when supported.
- Notification handling when the app is open, in the background or closed.
- User-specific notification preferences,
where supported.
- Appropriate handling of notification permissions.
Notifications should use Shivaizer's existing notification and workflow infrastructure wherever possible. The mobile application should not independently recreate notification rules. E. Approval Notifications
Phase 1 will include notifications for pending approvals, not a complete mobile approval-processing module.
Examples
- Purchase Order awaiting approval.
- Purchase Requisition awaiting approval.
- Sales Order requiring approval.
- Expense or payment request awaiting approval.
- Other transactions supported by Shivaizer's configured workflows.
Notifications should display appropriate summary information, such as transaction reference, approval type, amount where permitted, and date. Users should be able to open the relevant ERP transaction or approval screen where supported.
Actual approve/reject/send-back actions and full transaction-level approval workflows will be included in a subsequent phase unless explicitly agreed as an additional Phase 1 requirement.
F. Reminders
Support delivery and display of reminders generated by Shivaizer's existing systems, including:
- Scheduled business reminders.
- Follow-up reminders.
- Pending-action reminders.
- Due-date reminders.
- Other configured ERP reminders.
The mobile app should display the reminder, its date/time and associated reference where available. Reminder generation and scheduling should remain controlled by the existing ERP backend.
G. User Profile and Settings
- View basic user and company information.
- Logout.
- Application version information.
- Notification permission/settings handling.
- Basic preferences where required.
1. Future Extensibility — Mandatory Architecture Requirement
Although Phase 1 has a limited functional scope, the application must be architected to support incremental expansion across Shivaizer ERP modules.
Future capabilities may include
- Sales and CRM.
- Procurement.
- Inventory and WMS.
- Manufacturing and Production.
- Quality Management.
- Complaint and Field Service Management.
- Finance.
- HR and Payroll.
- Barcode/QR scanning.
- Document handling.
- AI Assistant and AI Agent integration.
The developer must implement a modular architecture with:
- Clearly separated feature modules.
- Reusable UI components and design system.
- Centralized API and authentication services.
- Consistent error handling and logging.
- Configurable navigation and permission-aware menu visibility.
- Reusable dashboard, report and notification components.
- Maintainable state management.
- Deep-linking support.
- Versioned API integration where applicable.
The architecture must allow future module features to be added incrementally without rewriting the Phase 1 application or disrupting existing functionality. Where feasible, configurable dashboards, report definitions and navigation should be delivered through backend APIs so that supported additions can be introduced without requiring a current mobile release. Native application changes will still require an app update where the new functionality demands them.
1. Technology Stack
Mobile application
- Flutter.
- Dart.
- Riverpod or Bloc for state management, with the choice finalized during technical design.
- Modular application architecture.
Existing Shivaizer platform
- Backend: Java Spring Boot.
- Frontend: Angular.
- Database: MySQL.
- Cache/configuration: Redis.
- Existing ERP authentication, workflow, reporting and notification infrastructure, as applicable.
Mobile integrations
- REST APIs.
- Firebase Cloud Messaging or an equivalent push notification service.
- Apple Push Notification Service for iOS.
- Secure local storage.
- Deep links.
- Google Play and Apple App Store deployment.
The mobile app must communicate with Shivaizer through secure backend APIs. Direct database access from the mobile application is prohibited.
1. Security and Quality Requirements
- HTTPS-based communication.
- Secure token and session handling.
- Server-side authorization and permission validation.
- No sensitive credentials or secrets embedded in the application.
- Secure notification payloads.
- Proper error handling and logging.
- Testing across supported Android and iOS devices.
- Performance optimization for dashboards and reports.
- Handling of network failures and session expiry.
- Compatibility with Shivaizer's multi-company/multi-tenant architecture, as applicable.
1. Deliverables
- Technical architecture and implementation plan.
- Flutter application source code.
- Android and iOS application builds.
- Login and authentication integration.
- Dashboard and report functionality agreed for Phase 1.
- Push notifications and in-app notification center.
- Approval notifications and reminders.
- API integration and error handling.
- Testing and bug fixing.
- Google Play and Apple App Store deployment support.
- Source code committed to Shivit Technologies' repository.
- Technical documentation and build/release instructions.
- Knowledge transfer to the internal development team.
All source code, project assets, documentation and relevant configurations must be handed over to Shivit Technologies under the agreed engagement terms.
1. Candidate RequirementsMandatory
- 3–5 years of relevant mobile development experience preferred.
- Strong hands-on Flutter and Dart experience.
- Experience delivering applications for both Android and iOS.
- REST API integration.
- Authentication and secure session management.
- Push notification implementation.
- Dashboard, chart and report visualization.
- State management and modular architecture.
- Git and collaborative development.
- Testing, debugging and app-store deployment.
Preferred
- ERP or enterprise application development.
- Multi-tenant SaaS applications.
- Java Spring Boot backend integration.
- Experience with configurable dashboards and reports.
- Firebase services.
- Deep links and notification routing.
- Secure enterprise authentication.
- Experience designing applications intended for future feature expansion.
1. Engagement Model
We are open to hiring an experienced individual developer or engaging a specialized mobile development agency on a project basis.
The developer must provide
- Links to live Android and iOS applications.
- Relevant project experience.
- Proposed technical architecture.
- Estimated delivery timeline.
- Commercial proposal with milestone-based payments.
- Post-launch maintenance and support terms.
Phase 1 will be contracted as a standalone deliverable. Phase 2 and subsequent mobile capabilities will be planned and estimated separately. The priority is to establish a reliable, secure and extensible mobile foundation for Shivaizer ERP, beginning with login, dashboards, reports, notifications and reminders.
Pay: ₹25,000.00 - ₹40,000.00 per month
Application Question(s)
- How many years of full-time professional experience do you have in Flutter and Dart, excluding internships and personal projects?
- Have you developed dashboards, charts, reports, or data-driven enterprise applications?
- Have you developed and deployed applications for both Android and iOS? If yes, please share the app links.
- Do you have hands-on experience integrating REST APIs and implementing authentication and secure session management?
- Are you comfortable working from our office in Noida Sector 63?
(Yes / No – please specify your current location and availability)
- Are you available to join immediately?
(Yes / No – please specify your exact notice period and earliest joining date)
- What is your current CTC and expected CTC?
(Please mention in INR)
Work Location: In person
📌 Flutter Mobile App Developer (Noida)
🏢 Shivit Technologies
📍 Noida