The user test network 102 can include one or more user servers 104 to handle software calls, APIs and other development needs of software 103, locally within the user test network 102. The user test network 102 can be a private network inaccessible to and from the outside networks, or it can be semi-private and connected with public networks, such as the Internet. An operator of the infrastructure 100 can provide a remote-enabled local (REL) application 106, which the user can receive and run in the user test network 102. The operator can further provide a repeater 110 and remote devices 112 to enable the user to develop the software 103, using a remote device 112. The operator in most cases is independent from the user developer team and may have no access to the user test network 102, other than commands and access granted by the user through the REL application 106. The software 103 may be a website and/or a web application, running on the RDB 109. If the remote device 112 is a smartphone or mobile computing device, the RDB 109 can be a mobile browser, such as Chrome?, Safari?, or another brand of mobile browser. Through tunneling connections, the ULB 105 and the REL application 106 connect with the remote device 112 and the RDB 109, where the RDB 109 issues the software 103 traffic requests on and from the remote device 112. A video feed of the display of the remote device 112 is captured and generated on the ULB 105, for the user to see and inspect the display of the remote device 112. Besides the display of the remote device 112 generated on the replica display on the ULB 105, the infrastructure 100 can also provide the user with various reports and logs and other test and development data about the connections between the ULB 105 and the remote device 112 and/or about the internal processes of the remote device 112, as they relate to the software 103. Test and development data may be accessible via a user interface (UI) element, such as a developer toolbar, as a feature of the REL application 106.