Ninox backend and its companion front end
For quite some time I slowly built an audio visual integration management suite. You can see the main menu of the backend on the left. But because AV Integrators primarily use mobile phones when installing the backend was simply not suitable. Even using the useful device type code that Ninox affords it was still clumsy to use.
Scott Dredge, (ninox partner) who introduced me to Ninox in the first place and provided a huge amount of support and encouragement (I am by no means a DB expert and as far as coding concerned...well best left unsaid) in getting the main DB off the starting blocks.
But the issue remained on how best to meet the needs of engineers on site installing AV equipment who need to refer to equipment lists, drawings AND capture serial numbers, MAC addresses and lots more besides.
On the right is the 'from the ground up' creation of a mobile friendly WebApp for Integrators to directly input (via API) all the information required to keep the database updated.
2 replies
-
Very cool Alan! Ninox needs this available for Ninox to allow non users to enter information natively.
Content aside
-
3
Likes
- 1 yr agoLast active
- 2Replies
- 179Views
-
2
Following