Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Flutter
Score 8.4 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
Drupal
Flutter by Google
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Drupal
Flutter
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Drupal
Flutter by Google
Features
Drupal
Flutter by Google
Security
Comparison of Security features of Product A and Product B
Drupal
7.8
70 Ratings
5% below category average
Flutter by Google
-
Ratings
Role-based user permissions
7.870 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.5
66 Ratings
3% below category average
Flutter by Google
-
Ratings
API
6.761 Ratings
00 Ratings
Internationalization / multi-language
8.357 Ratings
00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Drupal
6.3
74 Ratings
21% below category average
Flutter by Google
-
Ratings
WYSIWYG editor
5.467 Ratings
00 Ratings
Code quality / cleanliness
7.471 Ratings
00 Ratings
Admin section
6.974 Ratings
00 Ratings
Page templates
5.473 Ratings
00 Ratings
Library of website themes
5.564 Ratings
00 Ratings
Mobile optimization / responsive design
7.268 Ratings
00 Ratings
Publishing workflow
7.272 Ratings
00 Ratings
Form generator
5.469 Ratings
00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
We developed a corporate website using Drupal, which features a large number of static pages and several dynamic functions, including a contact us form, location finder, and job posting. We utilized Drupal with some customization to achieve the desired functionalities. We have also worked on e-commerce sites using Drupal, and there is a scope for improvements, specifically in cataloging.
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.
It has excellent security features and consistent updates.
It allows for extensive customization with the integrated themes and core code, especially when you first install it. This allows our dev team to get creative with marketing initiatives.
There is a large online community of Drupal users that consistently help answer any questions and issues
Security and new release notifications are a hassle as they happen too often
Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
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.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
It has a very steep learning curve. When starting with Drupal, the functionality and setup have to be learned, which is complex in comparison to tools like WordPress. Drupal is more powerful and can create a wider range of applications, but it definitely has a learning curve. I would recommend it to anyone who wants to make a dynamic web application bigger than the scale of a WordPress blog.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
WordPress for sure has a bigger community, a lot of paid extensions which sometimes is easier to purchase and get started, a lot of pre-designed templates to get you going, but nowadays with the scale of the projects we've been working with, and the need for custom-tailored designs, freebies and paid-extensions of WordPress is no good to us. For Forestry, since it's a Javascript CMS for exposing API, it's quite nice and all but compared to what Drupal can do, is quite limited, if it's just a blog-style website that you are after, Forestry might work as well, note that it's also a paid service. Craft CMS for sure got a lot of ideas off of Drupal, some of it's main features that they advertise is already in Drupal for years and I have not seen any benefits over Drupal, also it has a smaller community compared to Drupal
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.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
Drupal has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact.
Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact.
Drupal has allowed us to build great solutions for our clients which give them an excellent ROI.
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.