Enterprise AD teams need to realise that most traditional practices used to define desktop apps will not work with mobile due to device diversity, network connectivity and other mobile-specific considerations. And even though such means have worked historically, there are several reasons why these efforts don’t succeed today.
Essentially, even though mobile apps have been around since 1983 (the first of which was a contacts app for the Motorola DynaTAC 8000X – a ‘brick’ phone) and despite its rapid evolution, it still remains a new category for most. Research vice president at Gartner, Van Baker, explains that “users find it challenging to effectively describe what a mobile app needs to do. As a result, the traditional practice of having a business analyst sit down with the mobile app end users to define requirements for a new mobile application normally fails.” Such apps are also constrained by the nature of their platform and size of the screen they will be displayed on. This means that porting the workflow of a mature desktop app is not viable. This should be an important aspect for all AD teams as most complaints about mobile apps have to do with a poor user experience, which can be caused by poor user interface (UI) design, poor responsiveness or, indeed, poor application workflow. This just comes to show that desktop app development is an entirely different experience to that of mobile, including testing mobile applications shorter session lengths and limited presentation. But the important thing for enterprises to realise at this point in the mobile app maturity cycle is that there is still much to learn about how to design, build and deploy great mobile apps. And with the rapid pace of change in the mobile market is putting pressure on development and operations teams to adopt rapid development and deployment practices that constantly iterate their mobile applications as expectations change. So it’s crucial to understand how it is actually used, because behaviors may change. It thus becomes imperative to employ agile development to quickly iterate on improving the mobile app as the need for ongoing analytics to monitor how the app is used and confirm assumptions will not go away. This is due, in part, to the frequent release of new versions of mobile OSs and new devices. “Mobile apps are different,” said Baker. “They need to be frequently revised to meet end-user expectations, and this agile development process especially requires operations to be on top of infrastructure and systems to support frequent mobile app deployments and pushed updates.” Image sourceBy Shané Schutte
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.