Book Image

Learn Microsoft Power Apps - Second Edition

By : Matthew Weston, Elisa Bárcena Martín
4 (2)
Book Image

Learn Microsoft Power Apps - Second Edition

4 (2)
By: Matthew Weston, Elisa Bárcena Martín

Overview of this book

Microsoft Power Apps provides a modern approach to building low-code business applications for mobiles, tablets, browsers, and Microsoft Teams. The second edition of Learn Microsoft Power Apps will guide you in creating well designed and secure apps that transform old processes and workflows. Learn Microsoft Power Apps starts with an introduction to Power Apps to help you feel comfortable with the creation experience. Using screenshots from the latest UI, you will be guided through how to create an app, building your confidence to start developing further. This book will help you design, set up, and configure your first application by writing simple formulas. You'll learn about the different types of apps you can build in Power Apps and which one applies best to your requirements. In addition to this, you’ll learn how to identify the right data storage system for you, with new chapters covering how to integrate apps with SharePoint or Dataverse. As you advance, you’ll be able to use various controls, connectors, and data sources to create a powerful, interactive app. For example, this book will help you understand how Power Apps can use Microsoft Power Automate, Power BI, and Azure functionalities to improve your applications. Finally, you will be introduced to the emerging Power Apps Copilot tool, which uses artificial intelligence to accelerate the app building process. By the end of this Power Apps book, you’ll be ready to confidently develop lightweight business applications with minimal code.
Table of Contents (27 chapters)
24
Other Books You May Enjoy
25
Index
Appendix

User journey

So many times I have seen the user journey neglected by budding app developers. Again, I’ll hold my hands up and say that sometimes I’m so excited by the prospect of what my app could be, that I just dive straight in and start creating. This has then meant that I’ve ended up missing key considerations with what my user journey through the app is going to be.

What I’ve found more useful though, is by planning the user journey before I start writing. So what does this mean to you as a developer? It means that you need to firstly consider what does the user need to do in order to achieve an affect e.g. my user needs to use the app to create a new entry in a system, and my user needs to use the app to update an existing entry.

Once you have your key activities noted, you can then start to plan how the users achieve that. For example, if my user wants to create a new entry, they have to click a button to open a new form, which they then fill out and...