Mobile data collection has its digital roots in using a cell phone or tablet to collect data.
Due to the plethora of vendors and standardization around key buzz words, it’s exceedingly difficult to parse fact from fiction when assessing where to plant your digital flag.
The following seven questions, while the tip of the iceberg, are critical to include in your vetting process.
- How are offline environments handled? If your data collection is happening in the field, it’s inevitable that connectivity will become an issue at some point. Depending on how common this is for you, supporting offline collection may be absolutely required.
- How are permissions and access control managed? asdf
- How are projects/teams organized? asdf
- Can the software integrate with platform XYZ and what is setup like? asdf
- What is the recommended development lifecycle? Data collection will always be adapting. New fields, outdated formulas, and retired assets are just a sample of the changes you can expect. Development environments, data rollbacks, and data preservation through format changes will minimize project risk and improve user experience.
- What level of customization is possible for the frontend? For a field service app, we don’t need a “pretty” UI, but it needs to be effective. Look for customization options to the frontend that minimize errors, maximize collection speed, and incorporate branding to provide a unified experience for end users.
- Question? asdf
asdf
