Secure GPS expands mobile tracking options for organizations that need to offer an app with their own identity. This update publishes examples for a customizable mobile app, adds a JSON communication format, and lets an authorized user sign in with the phone as a tracking device.
The release also introduces fuel level statistics, expands available Teltonika sensor states, corrects Huabao interpretation, and makes sensor statistics more reliable when a period contains limited data.
Examples for building a custom mobile app
Example source packages were published to help integrators and businesses create a mobile experience connected to Secure GPS. The basic example supports an organization's visual identity, such as its name, icons, and startup screens, while retaining access to authorized platform functions.
The advanced example adds the ability to share the phone's own location and use it as a tracked device. It provides a starting structure for requesting location permissions, updating positions, and communicating with enabled public Secure GPS functions.
These examples are starting points rather than finished applications for every scenario. The team adapting them must review permissions, privacy, credential handling, battery use, publication in the applicable app stores, and ongoing maintenance.
Authentication and permissions retained in the custom app
The custom app uses Secure GPS credentials and respects the privileges defined for the user. An organization can offer its own mobile identity without creating a separate access model or granting capabilities the account has not authorized.
For a business with technicians, drivers, and supervisors, this relationship helps present only the actions available for each person's role. Administrators continue to manage users, devices, and permissions in Secure GPS.
Public integration credentials should be stored and used securely within the project. They should never be included in open documentation, screenshots, or the organization's public repositories.
JSON format for mobile applications
Secure GPS added a JSON-based communication mode for custom mobile applications. JSON is a structured format that represents the fields and values of a request or response clearly for an integration.
This option helps technical teams exchange information through a predictable contract and identify each value by name. The application should follow the expected public structure, validate responses, and handle errors or optional fields correctly.
JSON support does not bypass security controls or permissions. Every request remains associated with an authorized identity and the public capabilities Secure GPS allows for that flow.
Sign in with the phone as a tracked device
The custom mobile app adds an option to sign in while identifying the phone that will operate as the tracking device. If the device is already registered and the user has access, the app can associate the session with it. When the phone must be added, the flow presents onboarding according to account permissions and device availability.
After it is linked, the phone can send positions and appear in Secure GPS as an authorized device. This can support field personnel, technical visits, delivery teams, or temporary tracking situations where a phone is appropriate.
Continuity depends on location permissions, connectivity, battery, and mobile execution restrictions. The organization must also inform tracked people, obtain applicable authorization, and define when tracking should be active.
Fuel level statistics
Secure GPS adds statistics dedicated to fuel levels reported by compatible devices and sensors. The view helps users analyze how the value changes during a period and relate it to vehicle activity.
A fleet can use it to identify trends, review variations, and compare a change with position history. The data may support investigations of operational consumption or unexpected changes, but it should be interpreted alongside sensor calibration and characteristics.
Fuel level information is available only when the tracker transmits a compatible reading. Tank shape, liquid movement, wiring, and calibration can create variations, so an isolated reading should not automatically be treated as conclusive proof of refueling, consumption, or removal.
Teltonika sensor 2, 3, and 4 states
Teltonika compatibility was expanded to interpret sensor 2, 3, and 4 states reported by supported devices. Together with sensor 1, these inputs can add more operational context to each position when the hardware and installation use them.
An integrator may associate the inputs with ignition, doors, accessories, or other conditions, but their meaning is not universal. It depends on the model, wiring, and tracker configuration.
Available states can support maps, history, statistics, or alerts that accept the data. Before relying on them, installers should activate each input physically and confirm that Secure GPS presents the expected sensor.
More consistent Huabao message interpretation
Huabao protocol compatibility was corrected to process messages from supported trackers more reliably. This helps preserve the position and public attributes included by the device in the supported communication mode.
As with other protocols, final information depends on the model, version, and transmission parameters. Integrators should verify reception with the actual equipment and compare values with manufacturer documentation.
Sensor statistics with limited data
Sensor time statistics were corrected for periods in which the first reading does not yet contain a sufficient accumulated value. Secure GPS can use a valid baseline and continue the calculation instead of interrupting the query.
This is useful for newly installed devices, short periods, or trackers that begin reporting an accumulated value after the first position. Statistics reflect available data and do not invent activity time before received readings.
How this supports a service company
A company can adapt the mobile example with its own identity, assign access to technicians, and allow selected phones to work as tracking devices during visits. Supervisors can view their locations in Secure GPS according to defined permissions.
Across the same operation, fuel statistics help review trends while Teltonika sensors add more states. Huabao devices receive more consistent interpretation, and sensor queries continue working even when the selected period contains few samples.
Public technical summary
- Published basic and advanced examples for custom mobile applications.
- Brand customization with access governed by Secure GPS credentials and privileges.
- JSON format for public communication by compatible mobile applications.
- Phone sign-in and association as an authorized tracking device.
- New fuel level statistics for compatible readings.
- Sensor 2, 3, and 4 states in compatible Teltonika messages.
- Corrected public behavior for the Huabao protocol.
- Corrected sensor statistics when the initial reading lacks sufficient accumulated information.