LiveView puts live feeds from the WINK platform on iOS and Android, with the access rules already set in Media Router applied exactly as they are on the desktop. Officers, inspectors, and duty managers see what the operations center sees.
It can carry your own branding, so a citizen or a partner agency sees your service rather than ours.
Request Demo Read the Technical Brief
A mobile client for the platform, not a separate video system that happens to run on a phone.
Field staff are the people most likely to need a camera and least likely to have a workstation. The usual workaround is a laptop in a vehicle, a VPN profile, and a login that somebody set up two years ago. It is slow to open, awkward to use one handed, and it puts a device on the camera network that will spend its life in a car.
LiveView connects to Media Router the same way any other viewer does, which means the permissions, the camera sets, and the session authentication are the ones already configured centrally. There is no second access model to maintain, and nothing on the phone grants access to the network the cameras sit on.
Playback is tuned for the conditions field users actually work in: adaptive bitrate for cellular, multi-camera layouts for scanning, PTZ where the camera supports it, and event notifications so the phone can tell the user something happened rather than waiting to be asked.
Desktop monitoring is a solved problem: good network, mains power, fixed screen, mouse. Every one of those assumptions fails on a phone in a vehicle, and mobile video products that ignore the difference demo well in an office and frustrate everybody in the field.
A stream selected at the start of a session is the wrong stream a minute into a drive. Signal changes with position, sector load changes with the hour, and a moving vehicle hands off mid-stream. The real choice is between a stream that stalls and a stream that changes quality, and for an operational user a slightly softer picture beats a spinner every time. LiveView picks from the ladder Forge already produces, so the work was done once, upstream, for every viewer.
The question that decides most mobile deployments is what happens when a device is lost. If the phone holds a VPN profile and camera credentials, the answer involves rotating credentials and worrying about what was cached. If it holds an account that authenticates to Media Router and receives short lived session tokens, the answer is to disable the account.
The officer opens the app on the shoulder of a highway and sees the same cameras the operations center is watching, with the same permissions applied. They talk to the operator on the radio about a scene both are looking at within the same second or two. Nothing on the phone grants access to the camera network, and the account can be disabled from the same place every other account is managed.
Related: WINK Forge and WINK Media Router for the streams behind the app, and Why H.264 Is Almost Always The Answer on why hardware decode settles the codec question for mobile.
We will set up a branded build against your own streams so you can hand it to the people who need it.
Request Demo