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
Zeplin
Score 6.8 out of 10
N/A
Zeplin, from the company of the same name, is a platform supporting collaboration in application development by engineers and designers by providing an API with popular collaboration, development and prototyping tools and creating a space where productions can be shared and reviewed.
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 …
Zeplin is used for us purely as a handoff tool. It keeps it clean and clear for devs and product managers what is completed. It has some good labels and other organizing features. The different levels of access are also super helpful to give the correct people the view they …
As our project is large and there are many modules and they should be consistent. So, Zeplin's style guide can be shared globally across different projects and we can easily ensure consistency across all modules. Zeplin automatically exports assets in multiple file formats like …
Actually, we didn't select Zeplin. After a long time of internal discussions, the majority of the team decided that we want to move to Figma. We still use Zeplin as a legacy, but we don't use it for new features. In my opinion, it's less flexible than Figma, which allows …
We went without a tool like Zeplin for a long time, but as we grew we needed to get a better handle on the design process and handoff to engineering. We went straight to Zeplin off of numerous recommendations and didn't look back. We have had a great experience with Zeplin.
Zeplin is more focused on the handoff than in the creation itself. The other alternatives can do both, but Zeplin is an awesome tool for the handoff part. It depends in how big is your team and how the workflow is organized to understand whats the best tool for your team.
It was a business need from different departments. From an IT point of view, we have been a part of purchasing and setting up. However, the decision to go with Zeplin was not ours.
Out of all of the products that I have used to support design-to-development handoffs, Zeplin is my favorite. It’s pretty lightweight and easy to use (once you get the hang of it). Zeplin also has a smooth interface and is, generally, clearer to use than other tools, such as …
These other tools are really helpful products for creating and sharing wireframes / prototypes. However, Zeplin is the best tool for the actual hand off between the design and development teams once the design is actually ready to share. Zeplin fills this gap and improves the …
Zeplin is simpler. Zeplin lacks prototyping on par with Invision. Zeplin doesn't give a direct code for Android and iOS like Figma does. Zeplin doesn't have a lot of advanced features like Invision, for example, whiteboard. But Zeplin is good for at its job which is to share …
Zeplin is a really nice lightweight app, that is easier to use than Invision for sharing purposes. Invision does primarily handle prototyping, which Zeplin does not do. Abstract is my product of choice but is also a slightly different tool — almost a Github for design. It …
We chose Zeplin because it allowed our product and design teams to collaborate more effectively, while providing the rest of the organization an easily accessible location to access up-to-date assets. While InVision's interface can be more intuitive, we prefer Zeplin because it …
Marvel is a pretty expensive application for what it gives you, it is a pretty good tool but I think the handoff is not as good as Zeplin's. I think the style of Zeplin is more oriented to developers and Marvel is more oriented to the designers. I like the way Zeplin is …
Zeplin is great to inspect and share user interfaces, specifications and assets, perfect for developers. Tools like Invision and Marvel are much better to create prototypes for both developers, coworkers and even stakeholders, but they don't have this kind of feature …
For my company needs, Zeplin comes as the best tool in its category. Zeplin's competitors are great tools but they either offer way too many features or are priced above Zeplin with the same features.
Zeplin is in the right spot for both pricing and features.
I know there are other products out there but Zeplin has been so effective that I haven't even bothered to look elsewhere. The whole experience of Zeplin has been excellent. However, once Adobe XD is more built out Zeplin will finally have a formidable competitor as it will be …
Zeplin is much better when it comes to seeing the properties and CSS code of the design elements. Our developers love it when they get all that info from the Zeplin file.
Zeplin is the only solution tailored for this common use case. Previously we just shared files in dropbox but that was messy and didn't allow for specific comments, etc.
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.
I still have some issues, especially with color integration between the style guide and also project. When we update the colors, it's not automatically sync to every project. Aside from that, zeplin solves my problem for hand-off design from design to developer. I set zeplin is source of truth design file
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.
Zeplin's component management and style guide help us to be consistent across whole product and it so easy to use for non-technical person. It is now easy to collaboration for designes between different teams like stackholders, product owner, UI/UX, developers and testers. Now there is only one point of reference is Zeplin so it is so easy to get details without asking designer or developer again and again.
Zeplin has classic support with a chat from the website. It's working fine, and we're also getting the support needed when needed. However, Zeplin is very good at closing the incidents and moving on. It was a while ago we had a case with their support so that it might have improved since then.
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.
Out of all of the products that I have used to support design-to-development handoffs, Zeplin is my favorite. It’s pretty lightweight and easy to use (once you get the hang of it). Zeplin also has a smooth interface and is, generally, clearer to use than other tools, such as InVision. Plus, all of the plug-ins that you can use with Zeplin have supported the design-development relationship and workflows in which I’ve been involved in more efficient, clear, and effective ways than I’ve seen with any other product.
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.
We're using the free plan, so it fits in our needs, although we're limited to create only one project at a time
Sketch has some plugins that offers exactly what Zeplin does, for free
The integration with design apps (Sketch, Photoshop, XD) and collaboration (Slack and Trello) helps our team to better communicate and be notified on every update