Selecting Mobile Application development tooling
Conclusion: Organisations typically discuss the selection of enterprise mobility development in terms of web-based applications versus native applications, which quickly leads to debates regarding cross-platform tools versus standardising on one platform, such as iOS or Windows10. This is entirely the wrong way to think about enterprise mobile application development, resulting in unsustainable portfolios of fragmented and increasingly difficult to maintain applications. Instead, organisations should first identify the generalised use cases (i.e. common patterns of work) and seek to select mobile solution architectures (as opposed development tools) that meet each use case.
About The Advisor
Dr. Joseph Sweeney is an IBRS advisor specialising in the areas of workforce transformation and the future of work, including; workplace strategies, end-user computing, collaboration, workflow and low code development, data-driven strategies, policy, and organisational cultural change. He is the author of IBRS’s Digital Workspaces methodology. Dr Sweeney has a particular focus on Microsoft, Google, AWS, VMWare, and Citrix. He often assists organisations in rationalising their licensing spend while increasing workforce engagement. He is also deeply engaged in the education sector. Joseph was awarded the University of Newcastle Medal in 2007 for his studies in Education, and his doctorate, granted in 2015, was based on research into Australia’s educational ICT policies for student device deployments.