There’s plenty of alternatives to work with when your device is not yet ready. It’s just up to you which one will you pick for your project.
It should be a smart choice, though, so you get maximum advantages in possibly shortest time tailored especially for your own case.
Choosing this option will mean an excellent choice to debug users problems when the only available data are the data from the problematic moment in the app.
In fact, it doesn’t matter if you decide to start with communicating with the API, working on the app flow, UI components or storing/processing data on a device — you either get all the needed materials constantly during the process or before you even start. No problem, you can focus on another one in the meantime. Some parts of the app may be just really hard to test without the device, so they might not play their role according to our expectations later on. What I really mean is a sort of simulator, which would enable us to test the app and deliver additional values (I’ll expand it further). As it takes time to implement the solution, it’s really important to optimise your work and to focus on these, which are the most helpful in case of your project.1) If your prototype works (more or less), and you are pretty close to adding the communication module, you may consider this solution.
An intrusion detection system (IDS) is a device or software application that monitors a network or systems for malicious activity or policy violations.
Any malicious activity or violation is typically reported either to an administrator or collected centrally using a security information and event management (SIEM) system.
There are two biggest advantages of this solution: Another issue consideres data format.
It may be consistent with what you are planning to save on the device.