Flutter/Laravel Geolocation Control
Budget: $250 – $750 USD
I'm looking for a skilled developer who can help me implement a geolocation control feature in my Flutter application that targets both iOS and Android platforms. This feature is primarily intended for geofencing, specifically for security purposes.
Key Features & Requirements:
- The application is built using Flutter, and the backend is managed through a Laravel panel. It's important that the developer is well-versed in both technologies to ensure seamless integration.
- The geolocation control should be implemented in a way that it tracks the user's location only when they enter the app. It should not be constantly running in the background to respect user privacy.
Ideal Skills and Experience:
- Proficiency in Flutter for mobile application development.
- Strong understanding and experience in working with Laravel for backend development.
- Prior experience in implementing geolocation features, especially for geofencing purposes.
- Ability to ensure that location tracking is done in a way that is efficient, respects user privacy, and aligns with the security goals of the application.
If you have a strong background in Flutter/Laravel and have successfully implemented geofencing features in the past, I'd love to hear from you. Your insights about my needs and your proposed solution would be highly appreciated.
Documentation:
Documentation for Implementing Geolocation in the System
This document provides step-by-step guidance on how to implement geolocation functionality in your human resource (HR) management system, allowing users to clock in and out only when they are within a specific radius of the workplace. The implementation will be split between the administration panel (HR) and the employee mobile app.
1. Administration Panel (HR)
1.1 Adding Fields to the HR Panel
Three new data boxes will be added: latitude, longitude and area.
These fields will be incorporated into the user data entry form in the HR dashboard.
1.2 Database Update
Three new columns will be created in the database users table to store the geolocation data:
latitude: Stores the latitude of the work location.
longitude: Stores the longitude of the work location.
distance_radius: Stores the distance radius allowed for marking a point.
1.3 Modification of PHP Code
Only the PHP file responsible for inserting data into the database will be modified due to existing restrictions in the panel.
Validations and functionalities will be added to include new geolocation data during the insertion process.
2. Mobile Application
2.1 Application Features
Employees will log into the application using their credentials.
The app will request the location of the employee's device.
A check will be performed to determine if the location is within the permitted driving distance before allowing check-in or check-out.
Employees will be able to clock in and out only if they are within the specified distance radius.
2.2 Integration with Maps API
Integration with a maps API will be required to calculate the distance between the employee's current location and the workplace.
All necessary API functions will be implemented to obtain location data and calculate distance.
2.3 Security
The Maps API secret key will be kept securely in the application code to ensure the security of employees' geolocation data.
3. Operation Flow
3.1 Flow Manager (HR Panel)
The property manager enters latitude, longitude and distance radius data into the HR panel.
This data is stored in the database for each user, maintaining the security of the dashboard.
3.2 Employee Flow (Mobile Application)
Employees log in to the app.
The location of the device is requested and checked against the allowed distance radius.
Based on this verification, employees can register their entry or exit, ensuring the integrity of the geolocation system.
This implementation keeps the admin panel code secure and unchanged, while all geolocation-related checks and functionality are performed simply and centrally in the mobile app.
If you read my need, you will find the exact way I want this modification, which makes it a simple change that does not affect the original logic of the code.
I need a fair quote based on my needs. I included documentation because I know the code and its structure. I'm a Java developer and have a basic understanding of Flutter. If you haven't read my need yet, please go back and read it. Don't give me a quote without at least considering what I need.
Key Features & Requirements:
- The application is built using Flutter, and the backend is managed through a Laravel panel. It's important that the developer is well-versed in both technologies to ensure seamless integration.
- The geolocation control should be implemented in a way that it tracks the user's location only when they enter the app. It should not be constantly running in the background to respect user privacy.
Ideal Skills and Experience:
- Proficiency in Flutter for mobile application development.
- Strong understanding and experience in working with Laravel for backend development.
- Prior experience in implementing geolocation features, especially for geofencing purposes.
- Ability to ensure that location tracking is done in a way that is efficient, respects user privacy, and aligns with the security goals of the application.
If you have a strong background in Flutter/Laravel and have successfully implemented geofencing features in the past, I'd love to hear from you. Your insights about my needs and your proposed solution would be highly appreciated.
Documentation:
Documentation for Implementing Geolocation in the System
This document provides step-by-step guidance on how to implement geolocation functionality in your human resource (HR) management system, allowing users to clock in and out only when they are within a specific radius of the workplace. The implementation will be split between the administration panel (HR) and the employee mobile app.
1. Administration Panel (HR)
1.1 Adding Fields to the HR Panel
Three new data boxes will be added: latitude, longitude and area.
These fields will be incorporated into the user data entry form in the HR dashboard.
1.2 Database Update
Three new columns will be created in the database users table to store the geolocation data:
latitude: Stores the latitude of the work location.
longitude: Stores the longitude of the work location.
distance_radius: Stores the distance radius allowed for marking a point.
1.3 Modification of PHP Code
Only the PHP file responsible for inserting data into the database will be modified due to existing restrictions in the panel.
Validations and functionalities will be added to include new geolocation data during the insertion process.
2. Mobile Application
2.1 Application Features
Employees will log into the application using their credentials.
The app will request the location of the employee's device.
A check will be performed to determine if the location is within the permitted driving distance before allowing check-in or check-out.
Employees will be able to clock in and out only if they are within the specified distance radius.
2.2 Integration with Maps API
Integration with a maps API will be required to calculate the distance between the employee's current location and the workplace.
All necessary API functions will be implemented to obtain location data and calculate distance.
2.3 Security
The Maps API secret key will be kept securely in the application code to ensure the security of employees' geolocation data.
3. Operation Flow
3.1 Flow Manager (HR Panel)
The property manager enters latitude, longitude and distance radius data into the HR panel.
This data is stored in the database for each user, maintaining the security of the dashboard.
3.2 Employee Flow (Mobile Application)
Employees log in to the app.
The location of the device is requested and checked against the allowed distance radius.
Based on this verification, employees can register their entry or exit, ensuring the integrity of the geolocation system.
This implementation keeps the admin panel code secure and unchanged, while all geolocation-related checks and functionality are performed simply and centrally in the mobile app.
If you read my need, you will find the exact way I want this modification, which makes it a simple change that does not affect the original logic of the code.
I need a fair quote based on my needs. I included documentation because I know the code and its structure. I'm a Java developer and have a basic understanding of Flutter. If you haven't read my need yet, please go back and read it. Don't give me a quote without at least considering what I need.