Figma is a solid design tool to craft the UX design concepts/solutions for digital products. For printed marketing materials such as brochures, marketing flyers, press releases, etc, other design tools such as Adobe Illustrator, Photoshop, or InDesign might make more sense to use for those use case scenarios.
PowerApps is well suited for "quick-wins" and fast prototypes of business solutions. It also is beneficial for situations where business partners and developers work together - it allows the business folks to provide a "quick-and-dirty" prototype which is then fleshed-out by developers that are trained experts on the platform. The interactive and easy to understand representation of the solution allows business partners to "see" the solution and add, remove, or correct aspects of it themselves. It provides a common view and understanding of the actual solution across business units and tech teams. PowerApps, being a low-code\no-code platform is not well suited for business processes that require many complex computations or large amounts of custom code - such as solutions that are better architected as Web Site or "full-blown" desktop solutions. There are solutions that are just not easy or quick to accomplish in a low-code\no-code platform. Enterprise Architects should know the difference, however business partners often try to create a solution and only when stuck because it becomes too complex do they engage a tech team for assistance - at which point there are sunk-costs involved and hinderences to re-platforming the solution
Power Apps has formats that are pre-built that don't require any coding which makes it easier to achieve your vision. This does become a challenge if your App needs don't fit into that format.
We deal with a ton of data so the fact that you can connect to any data source in addition to their pre-stablished data connections makes the process a breeze.
The online learning resources and tutorials are helpful as well for those who are tech savvy.
Prototyping in Figma is pretty much nothing more than a glorified slide show. Sure, variables, etc are available but it takes way to long to set them up and even more time when there are revisions needed.
It would be helpful if there were a contextual help system for various functionality. For example, advanced autolayout (like space between) can become very tricky to implement sometimes. I often wish there were an AI assistant to ask for help. I often use ChatGTP to help me through these times.
Searching layers needs to be much easier and more intuitive.
I would like to be able to make groups like the layers palette in Photoshop. That would help with organization and speed a lot.
Figma is a pretty cool tool in many areas. My team almost uses it on daily basis, such as, brainstorming on product/design topics, discussing prototypes created by designers. We even use it for retrospectives, which is super convenient and naturally keeps records of what the team discusses every month. Furthermore, I do see the potential of the product - currently we mainly use it for design topics, but it seems it is also a good fit for tech diagrams, which we probably will explore further in the future.
It's easy to use for designers who are familiar with design terms and functions from Photoshop and Illustrator. However, non-tech and non-designer collaborators have a hard time figuring out how to leave comments and apply changes, compared to other online design tools like Canva and Squarespace. Even simple drag-and-drops and rearrangement of certain blocks become too complicated due to uncommon functions like Hug and Lock.
PowerApps is a great solution and I have spent the last year familiarizing myself with the platform and building custom applications to complete a whole range of tasks such as asset management, custom invoice generation, and item restriction tracking. We as a company have barely begun to scratch the surface of what can be achieved with PowerApps.
I haven't used their support lately but in the past, they had a chat that I used often. They often responded in a few hours and were able to give a satisfactory solution. I would imagine it's less personal now but the community has expanded drastically so there are more resources out there to self serve with a bit of Google magic.
The community forums are extremely responsive to questions asked, there is a good body of online documentation and many community posts to draw from. Although the platform has changed, which means some of the posts are out of date and the solutions provided aren't relevant. Of relevance, I read over 400 articles plus documentation to get this first app built in SharePoint, move it to SQL and make it work exactly the way it should.
In-person training has its own benefits - 1. It helps in resolving queries then and there during the training. 2. I find classroom or in-person training more interactive. 3. Classroom or in-person training could be more practical in nature where participants can have an hands on experience with tools and clarify their doubts with the trainer.
Online training has its own merits and demerits - 1. Sometimes we may face issues with connectivity or the training content 2. The way training is being delivered becomes very important because not everyone is comfortable taking online training and learning by themselves. 3. With the advancement of technology online training has become popular but there is a segment of people who still prefer class-room training over online one.
Figma compared to other tools has user friendly UI which is very easy for all levels of designers. Compared to Adobe XD and Sketch Figma is stable, while in other tools I have faced software crashing in the middle of the work which resulted in loss of data/design. Compared to other tools it's fast and shows less lag. Collaboration in Figma is very easy as it is cloud based but in XD it's not that smooth working with other designers.
Much cheaper, much more customizable, and easier to use. There is not much of a learning curve and the licensing cost is much cheaper. PowerApps does one thing very well, whereas other platforms are mediocre. There is much more customization possible for your in-house workflows that you can build yourself vs using NetSuite engineers to build it for you.
It has given us a focal point for development. We now have the possibility of connecting to mobile and the default SharePoint online interface isn't always easy to manipulate. PowerApps has given us an opportunity to improve our user experience.
An improved user experience has given us a better shot at compliance. When users don't fight the environment, they don't gravitate towards workarounds or non-compliance.
As lists and libraries change, the platform scales pretty well.
Having users with the capability to create their own forms and tools has dialed back the app dev need (there is a balance though) and distributed power to the process architects and people who actually need the solutions in the first place—much more efficient model of service delivery: self-service.
