Regarding Guideline 5.1.1(iv) – Privacy – Data Collection and Storage: We understand the concern regarding the location permission flow. Our application, Irontrac, is an asset management system that relies on location services to provide core functionality. Location access is used to help users track and manage the physical location of their assets efficiently. We would like to clarify that users are not forced to grant permission. However, if location access is denied, certain key features may not function as intended, which can impact the overall user experience. We ensure that users are clearly informed about why location access is required and how it supports essential app functionality. We respect user choices and only guide them to settings when necessary for enabling features they choose to use. We believe the updated implementation now complies with Guideline 5.1.1(iv).

Regarding Guideline 5.1.1(iv) – Privacy – Data Collection and Storage: We understand the concern regarding the location permission flow. Our application, Irontrac, is an asset management system that relies on location services to provide core functionality. Location access is used to help users track and manage the physical location of their assets efficiently. We would like to clarify that users are not forced to grant permission. However, if location access is denied, certain key features may not function as intended, which can impact the overall user experience. We ensure that users are clearly informed about why location access is required and how it supports essential app functionality. We respect user choices and only guide them to settings when necessary for enabling features they choose to use. We believe the updated implementation now complies with Guideline 5.1.1(iv).

Regarding Guideline 5.1.1(iv) – Privacy – Data Collection and Storage: We understand the concern regarding the location permission flow. Our application, Irontrac, is an asset management system that relies on location services to provide core functionality. Location access is used to help users track and manage the physical location of their assets efficiently. We would like to clarify that users are not forced to grant permission. However, if location access is denied, certain key features may not function as intended, which can impact the overall user experience. We ensure that users are clearly informed about why location access is required and how it supports essential app functionality. We respect user choices and only guide them to settings when necessary for enabling features they choose to use. We believe the updated implementation now complies with Guideline 5.1.1(iv).

Regarding Guideline 5.1.1(iv) – Privacy – Data Collection and Storage: We understand the concern regarding the location permission flow. Our application, Irontrac, is an asset management system that relies on location services to provide core functionality. Location access is used to help users track and manage the physical location of their assets efficiently. We would like to clarify that users are not forced to grant permission. However, if location access is denied, certain key features may not function as intended, which can impact the overall user experience. We ensure that users are clearly informed about why location access is required and how it supports essential app functionality. We respect user choices and only guide them to settings when necessary for enabling features they choose to use. We believe the updated implementation now complies with Guideline 5.1.1(iv).

Regarding Guideline 5.1.1(iv) – Privacy – Data Collection and Storage: We understand the concern regarding the location permission flow. Our application, Irontrac, is an asset management system that relies on location services to provide core functionality. Location access is used to help users track and manage the physical location of their assets efficiently. We would like to clarify that users are not forced to grant permission. However, if location access is denied, certain key features may not function as intended, which can impact the overall user experience. We ensure that users are clearly informed about why location access is required and how it supports essential app functionality. We respect user choices and only guide them to settings when necessary for enabling features they choose to use. We believe the updated implementation now complies with Guideline 5.1.1(iv).

Regarding Guideline 5.1.1(iv) – Privacy – Data Collection and Storage: We understand the concern regarding the location permission flow. Our application, Irontrac, is an asset management system that relies on location services to provide core functionality. Location access is used to help users track and manage the physical location of their assets efficiently. We would like to clarify that users are not forced to grant permission. However, if location access is denied, certain key features may not function as intended, which can impact the overall user experience. We ensure that users are clearly informed about why location access is required and how it supports essential app functionality. We respect user choices and only guide them to settings when necessary for enabling features they choose to use. We believe the updated implementation now complies with Guideline 5.1.1(iv).

Regarding Guideline 5.1.1(iv) – Privacy – Data Collection and Storage: We understand the concern regarding the location permission flow. Our application, Irontrac, is an asset management system that relies on location services to provide core functionality. Location access is used to help users track and manage the physical location of their assets efficiently. We would like to clarify that users are not forced to grant permission. However, if location access is denied, certain key features may not function as intended, which can impact the overall user experience. We ensure that users are clearly informed about why location access is required and how it supports essential app functionality. We respect user choices and only guide them to settings when necessary for enabling features they choose to use. We believe the updated implementation now complies with Guideline 5.1.1(iv).

Update user interface and functionality.

improve design and functionality.

Add Scan text functionality.

Update new design and style

Container module

Improve design and add new functionality.

Hot fix color band and other style issue

Stability improvements and UI enhancements

add asset button in list module and fix size and style issue.

hot fix issue fix, asset details and certificates button

Add Geolocation and activity tab in asset module, add new certificate button with new functionality and implementation share functionality

hot fix and implement new asset import functionality

update version, fix design related issues.

design related changes.

Date picker.

hot fix - job

- force update app functionality

work order related.