{"id":2,"date":"2022-07-31T14:55:40","date_gmt":"2022-07-31T14:55:40","guid":{"rendered":"https:\/\/mobilewhereitmatters.com\/?page_id=2"},"modified":"2022-11-29T19:50:28","modified_gmt":"2022-11-29T19:50:28","slug":"sample-page","status":"publish","type":"page","link":"https:\/\/mobilewhereitmatters.com\/?page_id=2","title":{"rendered":"About the Book"},"content":{"rendered":"\n

Based on my experiences in digitalization, UX, and mobile over two decades<\/a>, I have created a suite of tools and models to help you make the right choices \u2013 end-to-end through the design, development, and delivery process.<\/p>\n\n\n\n

As suggested below, the initial strategy work covers the entire Ecosystem of Apps, while the following five stages of App
development are on a per-App basis. Red dots indicate go\/no-go gates between stages <\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

Indicated in green above, the three parts of the book cover three broad phases:<\/p>\n\n\n\n

Part I: Strategy and Prioritization<\/strong><\/p>\n\n\n\n

Before doing anything, you must consider why you want to create a mobile App in the first place: Is there a genuine need for a mobile solution with the targeted audience ? Where can mobile make a tangible difference to your business ? A key element in your mobile strategy will be designing your Digital Ecosystem<\/strong>: How many mobile solutions (Apps or web) should you offer, what should each of them do, and how do they connect to, and interplay with, your “large screen” solutions ?<\/p>\n\n\n

\n
\"\"
A<\/strong> is a complex legacy system for HR purposes. B<\/strong> represents certain features which are made available for employee self-service on the intranet. C<\/strong> and D<\/strong> are mobile Apps targeting two specific use-cases: Employees driving their own car for company purposes (being eligible for a mileage refund) and blue-collar workers who must “clock” in and out of the factory, but don’t have easy access to a PC <\/em><\/figcaption><\/figure>\n<\/div>\n\n\n

Part II: Concept Development <\/strong><\/p>\n\n\n\n

Once you have a fairly solid idea about which Apps should be part of your digital ecosystem, and their individual purpose and target audience, you can start working on each App in terms of feature set, information architecture, and functional design. At this stage, you must dig even deeper into the everyday lives of users, ensuring that you support the User Tasks most relevant for mobile devices in a complete and coherent manner. A key model in this context is the Application Mountain<\/strong>, which will help you stay focused on your users and their mobile experience, rather than technologies. <\/p>\n\n\n

\n
\"\"
The Application Mountain model serves to keep focus on users rather than technology during the Ideation and Consolidation phases of App development. Hint: It’s much easier to descend a mountain from the top than to climb it from the bottom<\/em><\/figcaption><\/figure>\n<\/div>\n\n\n

This will also help you find the Minimum Viable Product (MVP) in your new App \u2013 starting with a small-ish solution first and adding more features later will not only minimize the risk of failure, but also increase the likelihood of success of your App<\/p>\n\n\n\n

Part III: Execution <\/strong><\/p>\n\n\n\n

With a solid (and user-validated) concept in place, the next step is getting your App to market. Plenty of important decisions must be made here as well, including how to ensure that your App successfully reaches the intended users. Of absolute essence is setting aside a budget for post-release development, so you can analyze user behaviour and adjust your App accordingly, after you have brought the first version to market. Designing your App according to the Onion Governance<\/strong> model will ensure post-release flexibility, allowing you to act quickly <\/p>\n\n\n

\n
\"\"
The closer you get to the core of the onion (i.e., your IT landscape), the stricter governance becomes. Closer to the outer layers of the onion, you can work progressively more freely<\/em><\/figcaption><\/figure>\n<\/div>\n\n\n

The book contains a total of 16 models like the ones mentioned above. The R.E.D. Scale for Digitization and Digitalization<\/strong> in particular has been a popular tool among my colleagues over the years.<\/p>\n\n\n\n

338 pages in full colour \u2013 6×9 inches.<\/strong> Available as hardcover (in Denmark), softcover (rest of the World) or e-book.<\/p>\n\n\n\n

\n
Buy Now<\/a><\/div>\n<\/div>\n\n\n\n

<\/p>\n\n\n\n

Table of Contents<\/h2>\n\n\n\n

Introduction: Be Relevant or Be Gone<\/strong><\/p>\n\n\n\n

Part I: Strategy and Prioritization<\/strong><\/p>\n\n\n\n

1 – A Brief History: The Three Eras of Mobile
2 – The Core Strategy: Mobile Where It Matters
3 – Elements of the Device Ecosystem
4 – The Bigger Picture: The Device Matrix
5 – Single-App Strategy or Multiple Apps ?
6 – Designing an Ecosystem for Your Users
7 – Outlines of a Business Case<\/p>\n\n\n\n

Part II: Concept Development<\/strong><\/p>\n\n\n\n

8 – The Five-Stage Development Model: Stage 1 and 2
9 – The RED Scale for Digitization and Digitalization
10 – The Application Mountain
11 – The “Minimum Viable Product” Approach
12 – Working with Push Notifications and Permissions
13 – Validate your Concept with Users
14 – Laying Out the Master Plan and Budget<\/p>\n\n\n\n

Part III: Execution<\/strong><\/p>\n\n\n\n

15 – The Five-Stage Development Model: Stage 3, 4, and 5
16 – How to Approach Pixel-Level Design
17 – App Icons and Naming
18 – Have a Development Strategy
19 – User Management and Access Control
20 – Validate your Design with Users Once More
21 – Understanding User Behaviour: Analytics
22 – Distribution to Users
23 – Post-Release: Unavoidable Maintenance
24 – Post-Release: Business Optimization
25 – Updating, Decommissioning, and Merging Apps
26 – Summary and Reflections<\/p>\n\n\n\n

Bibliography<\/strong><\/p>\n\n\n\n

Appendix: Index of Models<\/strong><\/p>\n\n\n\n

\n
Buy Now<\/a><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Based on my experiences in digitalization, UX, and mobile over two decades, I have created a suite of tools and models to help you make the right choices \u2013 end-to-end through the design, development, and delivery process. As suggested below, the initial strategy work covers the entire Ecosystem of Apps, while the following five stages … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-2","page","type-page","status-publish"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/mobilewhereitmatters.com\/index.php?rest_route=\/wp\/v2\/pages\/2","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mobilewhereitmatters.com\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/mobilewhereitmatters.com\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/mobilewhereitmatters.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mobilewhereitmatters.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2"}],"version-history":[{"count":14,"href":"https:\/\/mobilewhereitmatters.com\/index.php?rest_route=\/wp\/v2\/pages\/2\/revisions"}],"predecessor-version":[{"id":152,"href":"https:\/\/mobilewhereitmatters.com\/index.php?rest_route=\/wp\/v2\/pages\/2\/revisions\/152"}],"wp:attachment":[{"href":"https:\/\/mobilewhereitmatters.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}