The approach for solving business need with powerapps is seems a bit underrated when considering other content you are providing. For example the database relation diagram and wireframes you showed have quite impact on the final result. I would really appreciate mentioning similar kind of things alongside creating the app on the platform. I roughly listed domains that have impact on securely developing applications. For your upcoming videos, can you also provide your view on the best practices on: * backend part (how to create -or mock- reliable database system with sharepoint lists? What is your approach to split problem to digestable chunks?) * frontend part (how to use reusable components and how to have a consistent UI decisions?) * internal operations part (since there will be more users to use the app, how to do the role management, who will access which resources and which verbs (create/update/delete?) * development backlog part (how do you create user stories and how do you define the task is done? Do you employ any testing mechanisms like unit testing, user testing or any load testing ( for bigger applications)) * integration of other platform solutions such as power automate or power BI(reporting part is limited in both sharepoint and powerapps compared to power BI, how can we transfer the necessary parts to power BI.) Thank you for the fine work!
@@andrewhess123 Note: Sorry for the long message. Thank you man! If this got your attention, another pillar of successful powerapp implementation lets say, "selling" it to "the customer". How it is reflected to my job? i am not actually selling the application but I am selling the idea that would keep some of my current tasks out of my backlog and focus on this this only. Usually the I experienced some setbacks such as: * Users did not understand the flows because I used all of my time on application development but not on documentation. I had only myself for explaining things so I should allocate some time for documentation and should find a way to automatize the documentation part. * Users didnt like the idea of maintenance of data. or being the gatekeeper of it. This mindset pushes me to creating more like "stateless" application models. Input in output out, nothing kept in the system, only the "receipt" of user actions. * Users didnt "buy" the benefit of using powerapps instead of excel sheets. The main talking topics are present but besides generic information, what exactly this spesific application puts on the table. Because developing an excel template and developing an powerapp takes some development and testing time. * I couldnt be sure about scalability of sharepoint lists. I had some generic values for limitations but I coulnt be sure about how much traffic that the application would generate. Usually I refer the app as "wireframe" for actual app with real backend and dedicated developers maintaining the app. This is my next step plan for my powerap project. * Overall, creating application is apparently not only creating screens and lists, more like convincing people to use this thing instead old reliable but limited ability Excel files. Nobody confuses about "using" excel (they could be confused on content but this is other topic). But I am kind of introducing new way of working which affects multiple stakeholders.
@@muratcaglayan9242 This things you are saying are exactly how I feel. With citizen development people through out the door planning and maintenance and then also the ability to Scale. So, Thank you for the long replies and I totally agree!! Love the replies and ideas probably because I agree so much.
This approach (longer videos) are the way forward. I appreciate your proactive act. Have a nice day!
Thank so much Murat! Hope to keep getting better and better!
Have a wonderful day/week too!
HI andrew. You teaching is superb ! ( very detailed) and the length of the video is just aboout right. Thx very much for your teachings. Kind Regards
Thank you so much for the feedback Martin!
Thanks as always Andrew!
You too Eric, thank for stopping by!
hi Andrew , thanks for good video .
Hey Sarot! Thanks so much glad it was helpful!
The approach for solving business need with powerapps is seems a bit underrated when considering other content you are providing. For example the database relation diagram and wireframes you showed have quite impact on the final result. I would really appreciate mentioning similar kind of things alongside creating the app on the platform.
I roughly listed domains that have impact on securely developing applications. For your upcoming videos, can you also provide your view on the best practices on:
* backend part (how to create -or mock- reliable database system with sharepoint lists? What is your approach to split problem to digestable chunks?)
* frontend part (how to use reusable components and how to have a consistent UI decisions?)
* internal operations part (since there will be more users to use the app, how to do the role management, who will access which resources and which verbs (create/update/delete?)
* development backlog part (how do you create user stories and how do you define the task is done? Do you employ any testing mechanisms like unit testing, user testing or any load testing ( for bigger applications))
* integration of other platform solutions such as power automate or power BI(reporting part is limited in both sharepoint and powerapps compared to power BI, how can we transfer the necessary parts to power BI.)
Thank you for the fine work!
If there was a bigger emoji for ♥ i would give you one. Thank you so much for this!!!!
@@andrewhess123
Note: Sorry for the long message.
Thank you man! If this got your attention, another pillar of successful powerapp implementation lets say, "selling" it to "the customer". How it is reflected to my job? i am not actually selling the application but I am selling the idea that would keep some of my current tasks out of my backlog and focus on this this only.
Usually the I experienced some setbacks such as:
* Users did not understand the flows because I used all of my time on application development but not on documentation. I had only myself for explaining things so I should allocate some time for documentation and should find a way to automatize the documentation part.
* Users didnt like the idea of maintenance of data. or being the gatekeeper of it. This mindset pushes me to creating more like "stateless" application models. Input in output out, nothing kept in the system, only the "receipt" of user actions.
* Users didnt "buy" the benefit of using powerapps instead of excel sheets. The main talking topics are present but besides generic information, what exactly this spesific application puts on the table. Because developing an excel template and developing an powerapp takes some development and testing time.
* I couldnt be sure about scalability of sharepoint lists. I had some generic values for limitations but I coulnt be sure about how much traffic that the application would generate. Usually I refer the app as "wireframe" for actual app with real backend and dedicated developers maintaining the app. This is my next step plan for my powerap project.
* Overall, creating application is apparently not only creating screens and lists, more like convincing people to use this thing instead old reliable but limited ability Excel files. Nobody confuses about "using" excel (they could be confused on content but this is other topic). But I am kind of introducing new way of working which affects multiple stakeholders.
@@muratcaglayan9242 This things you are saying are exactly how I feel. With citizen development people through out the door planning and maintenance and then also the ability to Scale.
So, Thank you for the long replies and I totally agree!! Love the replies and ideas probably because I agree so much.
Is it easy to make it offline?