Browser-based approaches leverage the browsers now found on most phones. Today, your users' phones are likely to run XHTML Mobile Profile, a subset of XHTML optimized for mobile devices. Smartphones also support regular HTML and XHTML. Using a mobile browser for an application is relatively straightforward so long as the application takes into account reduced screen size, which varies depending on the device; minimizes the amount of data presented; and can tolerate inconsistent network connectivity. Applications should facilitate interaction by, for example, allowing the user to fill out a couple of fields on each screen, hitting Next after each one, as opposed to scrolling awkwardly across a large form.
Over today's 3G networks, browser operations are fairly snappy. But on slower 2.5G systems they can be quite sluggish, with users often having to wait tens of seconds for screen updates. Like SMS, the advantage of a browser-based approach is that you don't need application-specific client code, and you can support a wide range of devices, independent of the underlying OS. Also, there's no local data store, minimizing synchronization and security issues. The same application will work equally well on BlackBerry, Symbian, Treo and Windows Mobile devices. However, mobile browsers cannot support advanced Web technologies, such as ActiveX and JavaScript. In our RFI response, most application vendors provided some form of browser-based support.
A browser is OK for occasional data access, but it's not well-suited for frequent use; here a local client operation provides a much better experience. Moreover, the browser approach requires constant network connectivity.
For local client code, a Java client works across the greatest number of mobile devices. One common Java approach uses J2ME (Java 2 Micro Edition), in conjunction with MIDP (Mobile Information Device Profile) and CLDC (Connected Limited Device Configuration). These specifications define a complete mobile application runtime environment for mobile systems. The attraction of a J2ME approach is that this environment is available on a large number of devices, including mid-tier mobile phones, as well as all smartphone platforms.
J2ME has seen its greatest success with consumer applications, such as games, but it's increasingly viable for enterprise apps as well. Another Java approach, supported by IBM and SAP, is the RCP (Rich Client Platform), based on work by the Eclipse Foundation.
Verizon is demoing crowd analytics technology that uses 5G along with AI and mobile edge computing to give stadium operators insights into the flow of fans throughout a venue.
As we move closer to fully realizing the potential of Wi-Fi 7, it becomes evident that the RF, signaling, and throughput tests are not merely procedural checkpoints but the pillars of excellence in wireless communication.
With low earth orbit (LEO) satellites fast becoming the norm and 3GPP unifying telecom standards around the globe, the satellite IoT and machine-to-machine (M2M) sector ought to be looking at a bright horizon. But is this the case?
