Figma, headquartered in San Francisco, offers their collaborative design and prototyping application to support digital product and UI development.
$15
per month per editor
Flutter
Score 8.6 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.
$0
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
Project Manager
Chose Figma
1. Figma UI is easy compared to Adobe XD. 2. It is easy to share. 3. Available on the web, so can be used without an app.
I would recommend if you need to start from scratch a product UI or any customer journey that you need to implement that requires designing and visualizing different steps to complete a process. I would recommend that any design/UI/UX team brainstorm and make proposals that they can compare and discuss in a visual way.
Flutter by Google is well suited where you have to make an app across multiple platforms like iOS, Android, Web, Desktop and you don't have the bandwidth to create multiple teams for the Native app. This makes sure you have a faster development and you don't have to worry about how your product will look across different platforms. It is also very smooth/fast in response, making it close to feel like a Native app, this makes it an easy pick for a Fintech product where speed matters. Flutter by Google also has a huge library of Components, which are well tested and developed by Google's Flutter by Google team itself, making the development even more fast since the majority of required components are already available.
Figma allows us to create universal content. This means that if multiple designers want to re-use a piece of content, and if everyone's content should be dynamically updated from time to time, we can easily accomplish this by turning design elements into a universal instance. Then, if an update is needed, we can push the change out to all assets at once. It's very efficient and ensures we're all updating content accordingly.
Figma also allows us to set parameters for the company's brand guide and share them across various designers. This way, we can easily pull from approved brand fonts, colors, and more, which allows our assets to remain unified across multiple touchpoints.
Figma also allowed us to create and install our own plugin, which we use to export every slide we have in a frame at one time, versus the default export feature, which limits you to one slice at a time. This is particularly useful for us when we're working on email templates, since we tend to have a ton of slices in any given series.
It will be great if Figma will consider having the Pages where interactions can be stitched together among the Pages and not just one page with so many Frames to create the stand-alone clickable prototype that can be used to simulate the intended UX
Bring back the Inspect Mode tab right on the right-side panel of the main workspace instead of hiding behind the Dev Mode.
Figma Slides feature could be improved quite a bit more in order to be easier to assemble slides into a presentation deck and having pre-built templates for slides can be useful too.
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.
There's a bit of a learning curve, but generally I think it's both more powerful and intuitive that other UX design tools. Most of what I need to do as a designer can be done in this platform, from basic wireframes to creating a design system, to creating pixel perfect designs, to prototyping to dev handoff.
Flutter by Google is very easy to start with. The initial setup they provide is very helpful and easy to understand. The default project setup is also good and can be deployed to production without changing much. Flutter by Google provides a huge library of components, which are created and tested by their own team, making the development of application much faster and robust. Flutter by Google also has a huge community support where we can find components built by the community and we can contribute our own components as well, which helps in faster dev time. Applications developed using Flutter by Google are very smooth, almost feels like native, which helps in creating good impression on customers/clients.
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.
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.
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.
