Monday, September 7, 2015

Concepts for the company's use of mobile devices


In more and more companies move mobile devices in the first place when it comes to further increase employee productivity. Finally, the processing power of smartphones is sufficient today to perform more complex enterprise applications. Most, however, it comes at the right app strategy.


Regardless of whether apps are provided for field service personnel or for academic staff, this development opens boosting productivity to place a lot of potential, even the most demanding applications and data to mobile devices of the user. Moreover, the idea of employees who are always online, extremely attractive for companies.
With all the positive aspects, however, need to be protected applications and content before an illegitimate use and dissemination. Two approaches have been established there to meet this challenge: the Mobile Device Management (MDM) with the control of the terminals used for corporate purposes and the Mobile Application Management (MAM) with policies for the use of applications. In both cases, these approaches focus ensuring the safety, the regulated access and distribution as well as the reliable closure of enterprise applications.


Security is not everything

Security is certainly not everything. Often underestimated responsible as part of its initiatives for greater mobility, the importance of quality of use and deployment performance. If these neglected threaten mobile initiatives at the lack of acceptance of failure. The variety of devices and operating systems, diverging screen formats and different operating concepts, location-based services and highly variable in their performance mobile networks are just some of the complex parameters that need to be considered in the provision of mobile services.

Low tolerance for end users


It's no secret that the expectations of users steadily rising Apps - also and especially when used professionally. For a home to 84 percent of users say goodbye to an app, if they have a maximum of twice tried unsuccessfully to use this and an average of 65 percent of already filled with goods digital shopping baskets are virtually left due App weaknesses before it comes to buying.

Applying this behavior on the use of mobile apps for business purposes, this means in plain text: employees are not willing to tolerate crashes, slow downloads or unresponsive interfaces.

Concepts for the company's use of mobile devices consequently must have more to offer than solutions for the protection of data. In particular, a high quality of use for end users needs into specifications.

Mandatory for developers: Use quality back early in the focus

Front-end clients such as Web browsers for mobile devices are well documented, are stable and have positive operating concepts on. Mobile Apps, however, take the company in question in the duty to take to guarantee high performance and reliability values themselves in the development of software for the end user. The quality of the programming of an application has a direct impact on their performance and therefore needs to be considered early in the development process.

Application availability depends not only on the reliability of your code that comes natively on a particular terminal in a previously defined working environment for use, but also by the data services and APIs that are used by the app. Especially in mobile Web services (etc. links to social networking, authentication services, advertisements, analysis modules) have a negative impact on third-party, both the response time and the availability of Trans cations and work processes of the users.

Unstable power level in mobile networks

The power of the mobile networks differs greatly, even if a carrier and the terminal support the rapid LTE. Because even LTE-enabled devices automatically put back on slower network transfer rates when high-speed connectivity is unavailable or bandwidth at about traffic spikes are limited.

A feature of the mobile networks is that significant latencies occur when exchanging data. These often have a significant impact on the quality of use for end users. Because of these latency DNS queries can easily take each 250 milliseconds to complete and a single blocking Call an average of 500 milliseconds, which shows the same effects in the serial loading a page on a G3 network, such as the download of ten individual objects.

The account of the different formats of mobile devices as well as minimizing the impact of latencies of mobile networks can best be achieved by the following procedures:


• Focus performance at application design from the outset
• Stress testing in production (for mobile services)
• End-to-end analysis of the transaction performance
• Continuous monitoring of performance with simulated and real use technologies
• Elaboration of procedures in unforeseeable circumstances
• Focusing on application performance

Any company that developed a mobile service should classify its performance as an important feature. A common approach is to provide a 'power budget' set. Based on the definition of a standard - for example, three seconds to load - must be examined in deciding whether design or content, whether this requirement is not met. Run features to exceed the predetermined value, they must be removed or revised.

Stress testing in production


Functional and performance testing of mobile services during development are quite reasonable. But more important is to determine how the service behaves in the real application under peak loads is. The only way to elicit this, to determine the impact of the expected number of users in the context of simulations of traffic and activity on the service through.

Internet connections is real.


Mobile production environments create a larger scale and are of different external systems (e.g. As Web APIs, push notifications, analysis of the responses / applications) depending on which hardly can be considered in a simple test environment. Test environments, the use of cloud technologies based transactions are likely to be able to replicate the conditions that finds a user in productive operation. This type of load testing is to determine the quality of use, because it can take into account the access paths of the user, call the service with their mobile device at peak load times.

Continuous analysis of the transaction performance

The end-to-end analysis of the transaction performance refers to the measurement of performance and reliability that arise in the context of typical access and use means an end user within an application.

About exact web load testing can be errors and bottlenecks - perhaps even the causes of crashes Complete - notice. The aim is to identify problems in areas such as automatic garbage collection, the caching or connection to databases. In addition, can be gained extensive performance data in this way. Is carefully tested, enables end-to-end analysis of the transaction performance meaningful conclusions about the performance of networks, infrastructures and applications.

Continuous monitoring


Once an app is used by employees, companies should have a harmonized performance measure as 'clean room' set to obtain objective measurements. If the performance achieved deviated from the specifications, these values form the basis to identify potential problems. In addition, it is useful to correlate these results with the measured values, which are recorded in the use of services by users. As a result, a company has so monitoring data to both simulated and real users.

Emergency Planning


No system is perfect; it cannot change anything, the most extensive tests. Difficulties always occur - and in some cases even beyond this, the control of the owner of the website or app. It is thus important to establish the procedures for systematic errors in the preliminary. Although the third-party services or external systems fail, the main application can still - albeit limited - function, so employees can continue to be productive on the website or app. That leaves the room, corrections to the times, such as at night to lay, in which the system will not or hardly stressed.

Conclusion


Optimized use mobile services do not arise by chance. In order to face successfully the challenges of the digital mobile world, the look has to go, but on the requirements for security and compliance. It is important to classify the use of quality as a key success factor. Who dedicates the attention it deserves the quality of use of mobile services for employees, has done a lot for its successful adoption.

In addition, IT teams should be able to make the necessary corrections as soon as the system was adopted in productive operation. This requires a comprehensive monitoring of performance and availability in order to identify potential problems at an early stage.



No comments:

Post a Comment