There's a learning curve with any new tool, so it's going to be somewhere between a three and a four out of five in terms of ease of setup. It just depends on the person's experience and working with these types of tools, as to how well they understand and are able to work through that.

Once you have a concept of what to do, I'd say it takes less than two weeks to implement. With that initial building out of your very first PowerApps set of forms to accomplish what you're trying to do, you're going to tweak and enhance in the end. I just put this filter or search capability and sort capability on a couple of columns. Implementing new features and adding additional buttons, et cetera, will be something you are going to be doing along the way. You're going to continue to enhance it when you discover new capabilities you want to implement. It's a work in progress to roll it out and it's continual. That said, for the initial rough draft of something, from concept to actually putting it together, it's going to be just a week to maybe two weeks to do.

There is a learning curve for the initial cost of doing it. That said, I would definitely consider this a low-code job. It's definitely not high code. There's low to mid-level coding involved.

We're very limited in terms of users for deployment and maintenance. Staff within my office that would actually develop the PowerApps forms and implement and train up the other analysts are only going to be somewhere between three and four. They are program analysts themselves. They aren't IT.

The solution is deployed on a corporate cloud, so it is for the organization's private use. The time taken for deployment depends on the complexity. But, when I was working on Power Apps, it took me days. When they were responsive or needed to form a table, I needed to manually add blocks on top of each other, including everything in that, and that was taking a long time.

It's very easy to set up. You should have all the licenses available. It's quick and easy to implement, and you can get your hands on it immediately. It doesn't take too much time to get up and running. In contrast, its contemporaries like UiPath and Automation Anywhere are not so quick and easy to implement.

It's a stand-alone solution and uses connectivity to the software we want to automate. It's not hard to set up or to start automating things.

I'd rate the solution a four out of five in terms of ease of setup. It's not overly difficult. 

We were able to deploy the product in about a week. 

We have 50 to 100 people maintaining the solution. 

The initial setup was straightforward. I would rate it a five out of five.

Deployment took about a month once it was at my level and I fully understood it.

My implementation strategy was to meet with various business owners to identify a solution for them, then build and deploy that solution for them.

Setting up Power Apps is easy because it's a cloud solution. The deployment required one or two people and took one or two months. 

The solution is deployed on the cloud.

The initial setup of Microsoft Power Apps is straightforward. The implementation depends on the complexity of the application being deployed. It can range from one week to one month. I have not implemented an application that has taken longer than half a year.

The initial setup is very easy.

The initial setup is not complex. It's quite straightforward.

For me, just using it on my own, I just used Google searches or YouTube to figure out how do this or fix and tie items together. After about a month of learning and experimenting, I had a pretty good handle on how PowerApps works.

The initial process is simple. We need to create a trial and start working. It takes half an hour to complete. Later, we can purchase the licenses further.

The initial setup process for the solution is not complex. So, the company had made arrangements to help us manage the initial kickoff and deployment processes. Since it may not be a very easy process, it is more or less a mediocre one.

Because there were a lot of employees in my previous organization, it took around one year for the deployment process to be completed. Taking into consideration the environment, the initial settings, and the need to take care of security, the entire deployment process would take around one year.

The deployment process was carried out in three stages. If we consider the deployment's first stage, it is free for one year, though I can't recollect it entirely. However, I can say that it was related to Microsoft Azure since it was about security involving steps like how to create the security levels and which levels one can create. So, this process was carried out to create, considering our structure, resources, strategies in the company, security, and environment. The second stage involved the creation of real environments and splitting environments, divisions, and departments. The third stage involved communication and promotion. We then created the specific site devoted to the tools in Power Apps before creating a knowledge base consisting of general articles, specific articles, and the general question and answer section.

It’s straightforward to set up the solution. It’s not overly difficult or complex.

The initial setup is not complex or difficult. It's easy to set up. It's very straightforward. 

It took us about four to five months to set everything up. The apps vary in how long it takes to develop and release them.

The initial setup is easy because you don't need to write a million lines of code.

The initial setup was not straightforward, however, once you get a hang of it, then it's pretty simple to create things. From a documentation perspective, it's kind of a good guide that they have as far as Power Apps is concerned. It's easy to get started. Like any tool, you have to spend some time understanding and navigating around it. There is just a normal learning curve that is required as with application. You won't really find it that difficult if you are ready to invest the time to learn the tool. There's a moderate level of complexity.

It was not that effort-intensive, yet it definitely took us close to three weeks to create our first app on Power Apps, which was mostly SharePoint driven and had pretty decent complexities. It was not a very straightforward application. It took a fairly decent time. It was not a very long-term project, it was short-term, and we could manage to do it in three weeks.

We have not found it difficult to maintain Power Apps. It's pretty straightforward. We haven't had any challenges so far.

The setup is easy. In five steps you configure the dashboards and decide on data imports. 

IN terms of the initial setup, we have to choose which kind of approach we are going to use in PowerApps, as PowerApps has different strings. You can choose PowerApps Canvas, or you can choose a driving app, and that's a little bit different. In my case, I chose a PowerApps combo as I needed a little bit more in terms of flexibility and in terms of how I build this topic they screen. 

In terms of the development, it's quick, really it's quick, however, it's not the fastest way to develop and there are some other solutions in the market that are faster in some ways. In terms of deployment, in my experience, when you're going to deploy perhaps an application, you have to build a solution and a solution and it's a little bit tricky. You have to add all the components to the solution and, after that, you have to export the solution and import the solution into the production environment. We have an environment for development and a second environment for production.

The application is deployed, however, it's not in use yet. They are just preparing to start testing the application and once they finalize the test, the app is going to go live.

After I passed over all these little issues that I had, it was quick to deploy. It was just a question of minutes. When we export the solution and import the solution back, it's easy. However, all the processes to be able to finally get over these issues and everything, it took me four weeks just to realize what was going on and handle it. 

I think for the first-time user, the initial setup takes more time. Other tools like Automate are easier to deploy. PowerApps requires so many things to click and customize, it's really detailed. Building the system takes a little bit more practice than with other solutions. The deployment was done in-house and we had a couple of people working on it. The implementation took about a week. 

The initial setup is straightforward. It does not take long.

Maintenance is minimal. It is only one or two people who keep it running.

The initial setup is very straightforward and simple. It's not complex or difficult. 

There was some background development involved during the deployment process. 

The is no maintenance required.

The initial setup was easy, we had no problems. 

We have a small team that does the maintenance of the solution.

The initial setup is fairly straightforward. I would rate it a seven out of ten. 

The whole life cycle takes two months to develop, test, implement and deploy.

The initial setup was straightforward because they have a quite number of templates that you can pick from. The deployment does not take long as it comes with the Office 365. If you have Office 365, you have the Power App enabled in your directory.

The initial setup was very easy and quite straightforward. I would not describe the process as overly complex or difficult. A company shouldn't have any issues with the implementation.

For me, the initial setup was very simple and smooth-flowing.

The initial setup for this solution is very easy.

It was easy. We started in February, and everything had to be up and running in March because of the pandemic of 2020.

The ease or difficulty of the initial setup varies. For me, it wasn't that hard. However, I already had an Azure subscription and a Microsoft account. If you don't have any of that, it's not that easy - especially if you're not very technically inclined. It can be a daunting task.

I'd rate the ease of setup six out of ten. 

The deployment is fast and takes almost no time at all. I developed the application, and I pushed the publish button, and it was published.

The initial setup of Microsoft PowerApps is straightforward. 

For deployment, we use the ALM CoE kit, and GitHub through the pipeline. It is done through the team, creating a Dev environment for each pre-Dev and production environment. When we have completed testing and validation, we proceed with staging and then production.

We have not implemented using an automatic deployment through Azure Pipeline as there are a lot of bugs. We are still doing the implementation manually.

It is quite straightforward.

Our company is quite large. With 1,500 or so people, changes take a while to implement. It's not like a small organization where you can do everything quickly. You need to make sure people know how to use it.

In general, the full deployment took a few months.

We use the cloud version of the solution. There isn't an in-depth deployment process. 

Setting up PowerApps is easy, and I can do it by myself.

Initial setup is not very difficult. Even with minimal knowledge it's easy to understand. Deployment took somewhere around half an hour and it required one person to implement. We have four people in the company maintaining the solution. 

The initial setup is AI-infused. If you start working on an application, AI works for you in the background and tries to provision everything you need. I would like it to be a bit faster. Sometimes the designer just breaks and you get an error notification. 

The initial setup is extremely simple for me. I am an IT professional, but it is easy, even for others.

I have worked with many who have been using other tools and when they were introduced to PowerApps, they expressed that it is amazing.

It didn't take long for me to install, only a couple of minutes, because I've been using Office 365 since 2013, but I've never used PowerApps before. I started only recently, in 2018.

One of my clients asked me to create a small app in PowerApps for him. That's where we began. I had a PowerApps application ready in a week.

We don't require any maintenance as it is on the cloud.

The installation was very easy because it's already in the cloud. It took about 20 minutes to install PowerApps.

The initial setup was relatively straightforward. 

There isn't an implementation process for the product. It is on the cloud. Everything is pretty automatic. In that sense, it's rather straightforward. It's not overly complex or difficult. It's on the user accounts. I just go ahead and start creating my app from there.

The initial setup was straightforward, but if you want to put more options, it gets complicated.

The initial set up of this solution is fairly straightforward.

The initial setup was not complex. It's very easy as it's on the cloud. You don't need to be an expert in order to deploy it.

The initial setup was easy and straightforward.

It took approximately two days, but it depends on what features have to be implemented.

I maintain this solution myself, and it only requires one person for maintenance.

The initial setup is quite straightforward. A company shouldn't have any issues with the setup process. It's not overly complex. 

The initial setup is straightforward. It is a self-service solution, so there is no real deployment. It is a case of enabling that functionality within the Microsoft account, and then telling the people that it is enabled and available. At that point, I think that that they can create their own applications if they need to.

The solution is very easy to set up. Deployment is almost instantaneous. It's on the cloud, so you connect the logins and it's ready to go. You don't have to download it onto any device.

Although I'm not the person who handles the initial setup, my understanding is that it's not too difficult and pretty straightforward.

Deployment typically takes two months. The last deployment we did started in May and was completed by July.

There isn't a lot of maintenance needed. We have one developer that's dedicated to the maintenance and changing the environment as needed. It's pretty hands-off though.

The initial setup is not overly complex or difficult. It's pretty simple and straightforward. 

The initial setup was very straightforward. I tend to think the documentation and the community forms are more than enough to help improve your setup experience. It's very, very, straightforward. I don't think it took more than five minutes to set up and that's amazing. Previously, it might have taken a week to complete setup - all the code, database, linking. 

The initial setup is pretty straightforward. They have a lot of third party connections. It's easy to connect things if you need to. However, this can add to development costs. That said, it's nice to have the option.

The initial setup is straightforward.

It is easy to deploy, although we have some experience.

It seems pretty straightforward.

The initial setup is quite easy, it's as simple as turning it on.

It took us two weeks to deploy it and to come out with the first prototype.

Microsoft PowerApps is simple to install.

Setting up PowerApps isn't straightforward. We allow users to be citizen developers, as they call it, and around 95 percent of the time they end up going back to us, saying, "Hey, we can't use this. We don't know what to do. Help us!" As IT, we're spending a lot of time creating these forms for them instead of users doing it themselves.

As the solution is deployed on-cloud, there is no need for installation. 

As always - depends on the size and complexity of the needed solution. But the cloud based solution + the Low Code approach simplify it. 

The initial setup is not complex, but there were some areas that we struggled with, such as the gallery limitation. Nowadays, we are able to pull more than two thousand records, but if we do so, we have a lot of problems with the performance of Microsoft Power Apps.

The initial setup is very easy because it is a SaaS solution. We don't need to implement any server in the company. We just use the SaaS solution.

In terms of the implementation strategy, we take a small business use case in the financial area and do a proof of concept to evaluate a solution. 

The initial setup was very easy. It's a cloud solution. Because we were already using Microsoft products, we only had to enable the license and just start using it.

The initial setup was not easy, but not exactly complex. There was a lot of research.

It doesn't require any installation. PowerApps works on the Microsoft cloud on the server, and you have two options for using the data. The data is possible on-premises or on the cloud, but PowerApps is only on the cloud.

The initial setup is no more complicated than similar solutions. I'd say it's pretty straightforward. 

The initial setup is easy. It is hosted in the cloud, so it is ready to go.

It is very easy to install. It takes no time because it just talks to the cloud.

When it comes to installation, we need to install a gateway and integrate between two tools, for example, PowerApps and Power Virtual Agents, Deployment is a little complicated. The data is available in Google but it's a little difficult.

The install is not a problem at all, it did not take very much time.

The initial setup is moderately complex.