Flutter is an open-source mobile application development framework created by Google. It is used to develop applications for Android and iOS, as well as being the primary method of creating applications for Google Fuchsia.
N/A
Power Apps
Score 7.7 out of 10
N/A
PowerApps is a low code / rapid application development product from Microsoft that allows users to quickly build apps.
I have experience with react and react native. I would say that the idea behind all those frameworks are quite similar. However, I found the javascript-based frameworks a bit more accessible as you could utilise your javascript knowledge. Here, Flutter works with its own …
- Like it better than other solutions, or building native on both platforms. - React Native has a good advantage with language and amazing web support. - React Native is easier to jump in for web engineers.
I have not used Dev Express Universal and Selenium Web Driver much besides in the demos that were provided to our company. We compared the demos and went with Google Flutter because it worked well and looked noticeably better than the other products. While I am unsure of the …
Flutter is a bit different from Android Studio, the latter one being an Integrated Development Environment (IDE) while Flutter itself is a Cross-Platform Mobile Development SDK (Software Development Kit). Flutter provides the access to the native features and built-in plugins …
I selected Flutter because of Flutter's awesome, pre-build UI components. It makes my life as an indie dev easy and fun. At the time, I had never built an application with React Native, so this was a fantastic introduction to cross-platform development. That said, as someone …
I think that Flutter is now much better than Microsoft's Xamarin and the old Apache Cordova. I was able to go from a concept design to a working application in almost no time and with almost no experience with Dart at all. It helps (but it is not a requirement) to have some …
Way less tweaking to have a cross-platform experience, better performance, and feels more like a native app. But the community, while growing, is still smaller than React Native. This can cause issues with specific use cases as it's harder to find help online.
React Native seemed like a comparable and equally valid choice to Flutter. Performance, ease of development, and support are roughly equal between the two products. Dart, to me, felt easier to work with than Javascript or Typescript. Flutter SDK tools and VSCode extensions made …
The app generated by Flutter doesn't change upon OS versions as in native apps or other cross-platform apps. The running speed of apps is much faster than its competitors like react-native and Cordova. It's lightweight and faster to compare to other cross-platform. The hot …
The main alternative to Flutter I have experience with, is Qt framework. For a long time, Qt was the go-to if you wanted a cross platform desktop application, probably written in C++ or Python, that could take on the 'look and feel' of the target platform. However, Qt is …
I think Appian has all major features and my Manager gives this 2 tools to choose one from that. I found Power Apps is easy to learn and develop, but I feel Appian is realy complex. I strugles to learn something in Appian but that didn;t works well. Power Apps gives me …
1. PowerApps functionality comes with E1 over E3 License without adding extra costs 2. For Nintex you pay (at the beginning) for each workflow, so my intention would be, to do no workflows to prevent additional costs, but I want a platform with a fair price that allows me to …
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 …
PowerApps includes several features and caters to several business needs. Bubble is not Microsoft, people using PowerApps find it convenient since they are already committed to Office 365.
PowerApps and Power Automate go together in the Power platform. They are made to work together to create a vast collection of connectors and out of the box pieces that come together to make a whole application. If you are unable to complete a task from within PowerApps, Power …
I have extensive experience with another low code platform, K2 and it's SmartForms. SmartForms have their own challenges but allow the developer to extend the operation of a form as needed. In addition, their vNext version promises to greatly enhance the developer and …
PowerApps is the first we have used in Office 365 and Azure Integration. It really helped us to integrate application in Azure and building short apps with low cost.
PowerApps has much power when talking about Office 365 and Azure integrations. Has low cost and it is easy to create/deploy applications. Bonita is open-source but it is necessary to have many technical skills to create applications and also to handle the infrastructure when …
I'm not sure if you can say D365 CRM is an alternative to PowerApps, because basically all the customization of using D365 CRM, or what used to be called XRM, is now called a model-driven PowerApp. Likewise, SharePoint has become intimately connected to canvas PowerApps. Both …
PowerApps is what the company has presented to us as our option. While Nintex is nice and relatively capable, it is always a +1 to the Microsoft platform and requires its own validation and integration. Nintex can also be feature limited in its online version depending on the …
It's by far the most superior simply because of its integration with what most companies already have in place Sharepoint, SQL, Azure. It's drag and drop functionality is top notch and the dream of creating mobile apps without having to duplicate the work is amazing as well. …
Along with PowerApps we evaluated Smartsheet for use and we determined that PowerApps provides a great deal more functionality and flexibility. Especially when you consider it is nested in SparePoint and all the additional functionality that SharePoint provides. PowerApps …
Although Zoho allowed for some unique customization abilities including html styling and simple scripting language. In the end it came down to the Office 365 and choice of many other connections that lead me to choose PowerApps.
Flutter is well known for native app development, if you have android studio installed on your system, you can quickly start using it. This might not be the best choice for you if you do not wish to learn a new language, i.e. Dart and you do not know it already.
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.
Occasionally updates to the Flutter SDK result in wide-sweeping changes that seem to not be thoroughly tested and considered. Flutter sometimes evolves too fast for its own good.
While the 3rd-party Flutter package ecosystem is vast and rich, 1st-party support for basic things (audio/video playback, battery information, Bluetooth services, etc.) are lacking. You are occasionally forced to rely on an open-source package for use-cases that other platforms have native support for.
Documentation, particularly around testing, is lacking. While there are some great docs, like the Dart Style Guide, many Flutter-focused support documents are lacking in quality and real-world usability.
Flutter allows you to architect an app however you want. While this is a great feature, it also adds complexity and leads to the current state of Flutter's state management, where there are 50+ options on how to organize your app, with very little official guidance or recommendations from the Flutter team. For a beginner, this can create decision paralysis.
PowerApps has a great coding option, but there are some pieces of the tool that the requirement to understand code is a barrier to fun if the user doesn't code.
MUCH time can be spent looking for solutions on this young platform and the body of forum/help/lessons learned is not as robust as it will be in a few years.
Like many early-stage Microsoft products, PowerApps is a relatively blank slate that will be improved by the feedback of their users and ongoing feature development. Right now it seems that the product lacks a critical mass of use-case driven templates (there are some, but I haven't yet found one that didn't require more work to customize it to my need that it would take to build my own tool).
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.
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.
I have experience with react and React Native. I would say that the idea behind all those frameworks are quite similar. However, I found the javascript-based frameworks a bit more accessible as you could utilise your javascript knowledge. Here, Flutter works with its own language. This has advantages and disadvantages sometimes. I found the community around javascript frameworks bigger and therefore sometimes more helpful. However, Flutter does a good job here as well. I think the main argument for Flutter is its usability for less experienced developers. If you do not have knowledge in javascript or other programming languages then I think it is much easier to start with Flutter than with another framework like react. I think the package that you get form scratch is better than in the other frameworks were you have to set up and learn a lot more before you can start.
1. PowerApps functionality comes with E1 over E3 License without adding extra costs 2. For Nintex you pay (at the beginning) for each workflow, so my intention would be, to do no workflows to prevent additional costs, but I want a platform with a fair price that allows me to create workflows without thinking about the price for each workflow and we use only some workflow and relative easy workflows and forms as a medium-sized company. 3. PowerApps provides a lot of functionality without needing to invest in premium features directly.
The rapid development capabilities of Flutter allow us to build apps we could not have previously considered commercially viable, opening new revenue streams.
Free and open licensing made adoption very easy (ie. free/low cost!).
In comparison to Qt, our time spent arguing with build tools and perfecting development environments has decreased substantially.