Lytho Workflow vs. Power Apps

It's a flexible program that can be molded to fit most businesses. It's geared towards agencies but we've been able to use it successfully as an in-house solution. It's pretty intuitive for the most part and is easy for new hires or clients to get up and running pretty quickly.

Incentivized

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

• Requests - Request forms are set up so that certain fields are required and there's a minimum turnaround time. This prevents others from submitting an incomplete request or requesting things last minute.
• Proofing - Chasing after people to approve a proof is always a pain, but the simplicity of Lytho Workflow makes it less of a pain. I can quickly remind people in the route to review the proof by clicking a button.
• Templates - I use templates so that a list of tasks is created for me when I accept a job. It also creates a timeline for when each task needs to be done.

Incentivized

• 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.

Incentivized

• Not being able to permanently delete inactive/old users (i.e. employees that are no longer with the company).
• Search filtering features are lacking.
• Not being notified when someone replies to my comment without @ mentioning me.

Incentivized

• More complicated to understand in comparison with Nintex Forms.
• Complicated to find errors.
• Using PowerApps for SharePoint Forms is a bit complicated by setting up the start and load scenario with a lot of JavaScript.
• Load values, change them by code, and save them back could be easier. Actually quite complicated to handle a lot of variables.

Incentivized

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.

Incentivized

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.

By consolidating the requests, project management, and proofing without features we didn't need like invoicing it was an easy fit for us. We were able to quickly develop a comprehensive workflow and the gains to efficiency were immediate. Pricing was competitive (at least at the time) and the implementation was very good as well.

Incentivized

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.

Incentivized

• I wasn't working for the company when they first started using Lytho Workflow workflow, so I can't say what impact it has had. However, I do see the product as a necessity in the fast-paced environment that is retail marketing. The introduction of the new "change request" feature has saved countless hours of miscommunication and confusion when project objectives change.

Incentivized

• 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.

Incentivized