Power Apps Navigation Design: Containers Vs. Galleries
HTML-код
- Опубликовано: 10 июн 2024
- Power Apps Navigation Design: Containers Vs. Galleries
Hey Everyone,
In this video, we are going to do a side-by-side comparison of how designing of Power Apps navigation looks when using containers and galleries.
Table of contents
Introduction 00:00
History lesson 00:54
Review the canvas app 01:56
Container Vs. Gallery
1) Response design 03:53
2) How many controls are used 05:45
3) Adjust control level 07:58
4) Data source for navigation 10:06
5) Useful for navigation screen 12:23
6) Paste inside each other 14:35
Conclusion 18:07
Helpful link(s)
powerapps.microsoft.com/en-us...
learn.microsoft.com/en-us/pow...
learn.microsoft.com/en-us/pow...
#PowerApps #PowerPlatform
Contact information:
Twitter: / dchristian19
Facebook: / www1.christianfamily.biz
Instagram: / dan.christian.33
LinkedIn: / danchristian19
Join this channel to get access to perks:
/ @danielchristian19 
Наука
You always make things easy to understand!
Thanks for the compliment, Krinrebj.
Very insightful and interesting comparison. Looks like Containers are the way forward in terms of navigation, at least depending on the design style one chooses. Will bear this in mind going forward. Thanks for sharing again.
Glad it was helpful!
Fantastic work Daniel,
Very clear, excellent
Glad you think so!
Great video as always!!! Thank you Daniel!!
Glad you enjoyed it!
Semi-related to this: what's considered the "best practice" these days for a persistent navigation element, like a toolbar that would appear on every (or many) screens in an app? I've got a couple apps out there where I spent (a lot) more time creating the toolbar in a component, thinking it would be easy to reuse that component in other apps. Practically speaking, most of the apps I've built have had navigation requirements that would have required just as much time to modify the component for that particular case.
The main difference for me is when you go to an uneven number of items or when hiding dynamically based on user permission level. Container solution fills the gap by stretching out left over containers (eg. 3 small in row 1 and two larger in row 2), therefore the screen is always populated entirely, no feeling that something is missing.
The question now is if it is for you more important to fill the screen and therefore have lot more work when you want to change something or if you want to have an easy to maintain screen than can be even copied from one app to another (or used as a component) but with empty space on the welcome screen.
Good easy explanations! Suggestion to name your title as the screen name, so you don’t have to prove on which screen you are
Great suggestion!
Great video, thank you.
Glad you liked it!
Thank you so much for the information. Really enjoyed it, I was wondering as an idea - Deep linking so I have watched many videos on deep linking for Power Apps and I would like to have a deep linking into the mobile Power Apps app. I have seen ways for notifications to the device that will deep link you into Power Apps app but I was thinking of the term of the deep link being added into a Document throw Power Automate or in a task in Planner. Please let me know your thoughts on this man maybe reach for more information if needed. Thanks again for the gallery VS containers. Keep up the awesome video's.
Hello Daniel, Can you share the first slide with the timeline of the PowerPlatform elements?