Figma, headquartered in San Francisco, offers their collaborative design and prototyping application to support digital product and UI development.
$144
per year
Flutter
Score 7.8 out of 10
N/A
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
Pricing
Figma
Flutter by Google
Editions & Modules
Professional
$144
per year
Organization
$540
per year
Starter
Free
No answers on this topic
Offerings
Pricing Offerings
Figma
Flutter
Free Trial
No
No
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Figma
Flutter by Google
Considered Both Products
Figma
Verified User
Anonymous
Chose Figma
Figma was a huge turning point compared to its competitors, especially Adobe XD, a tool designed for the same purpose as Figma. I would say that it and all the other tools I mentioned, including those that do not have the same focus on UX design (Photoshop and Illustrator), …
Adobe XD is an absurd copycat that never got to have even 10% of Figma's features. It's hyper fast because it's native, but that's the only good thing it has.
Axure RP is an excellent prototyping software, with Local Variables and complex interactions. But it's also extremely …
Compared to Adobe XD, the Figma tool is much easier to use, offers more features, and has a much lower cost. Its features are less complex, making it very easy to teach beginners how to use it. The navigable prototype is also easier and more efficient to share in Figma compared …
Figma easily wins against adobe XD. Asset sharing on XD was a pain. Figma makes it really easy by allowing you to export any layer as an asset. XD had no comments making it incredibly hard to communicate with the designer in remote settings. XD's prototyping system was not good …
I learned UX Design using Sketch and my team was using Sketch when I joined. We no longer use Sketch, and therefore I cannot compare its current functionality to Figma, but at the time of our switch, Figma just had more advanced capabilities- better collaboration, auto-layout …
Miro is more user-friendly than Figma, but is less robust in terms of web prototyping and graphic design. While Figma isn't made to be used as a design tool, our team has taken to using it as such because it's richer in functions and personalizations compared to Miro and Figma.
Better auto layouts, components and prototyping capabilities. Variables in Figma are also a fantastic addition to create a robust, and scalable design system. I use these features all the time. Love them!
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 …
I prefer to use it comparing to Adobe Xd. It surely is more intuitive and still develops itself providing new features (e.g. variables; however, I had to get used to the new interface). Now, if I had to compare it to Axure it'd depend on the project I'm working on. In case of …
Figma is the only tool that was build from the ground up for enterprise level distributed teams. If I were a one man shop or even a small team, I would consider sketch or other cheaper alternatives. For a large enterprise team, the only winner is Figma.
Figma is the go-to design tool that can be pushed to production very easily with developer tools. In my opinion it's the most complete design tool that considers the entire design process including the creation of solid design systems, high-fidelity prototyping, user testing, …
I think Figma is better because it's easier to create more visually appealing work. I would say that Figma is better for people who are used to using this sort of visual design software/platform. Whereas I think Miro is better for first time users, it doesn't offer as many …
Figma is the best for collaborative work. Very easy to learn, so easy that most people dont use it properly (which is good and bad at the same time). Prototyping is where I'd wish it will improve. Axure was awesome.
Figma is way better than Adobe Illustrator because of its ability to seamlessly integrate multiple use cases like mobile design and vector-based shape building. While Adobe Illustrator is great for adding texture and depth to illustration you can still build high-end …
In comparison to Figma, other tools which can accomplish similar tasks (Adobe XD, Sketch, and Adobe Photoshop) feel outdated, clunky, and lacking in functionality.
When switching over to Figma, the experience feels much more elegant, convenient, and cutting-edge in a number of …
Figma is the most efficient tool for teams and sharing with clients. It's also easier to learn than other Adobe products. When sharing designs with clients, Figma looks more professional than Canva.
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 …
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.
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.
Tappable overlaid layers - bugs on fixed components, such as an app navigation footer in a prototype
Swapping a component but retaining inputted copy or imagery.
Performance on prototypes to work better in UserZoom - having to delete hidden layers manually, optimize images, and streamline the file, in general, is time-consuming
Folder structures - larger teams need multiple layers of folder structure to help find things.
Branch performance - we need better, more user-friendly solutions to get designs to merge better.
Branch performance - branching with the option to choose which pages you want in the branch without deleting each page you don't need.
Default sharing options need improvement.
Responsive ratios' in prototyping without having to recreate pages.
Better collaboration with Jira to bring in links in the design mode not just dev mode.
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.
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.
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.
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.
I learned UX Design using Sketch and my team was using Sketch when I joined. We no longer use Sketch, and therefore I cannot compare its current functionality to Figma, but at the time of our switch, Figma just had more advanced capabilities- better collaboration, auto-layout tools, prototyping, etc. From what I can tell, it remains best in class for UX Design tools.
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.
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.