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
ServiceNow Now Platform
Score 8.6 out of 10
N/A
The ServiceNow Now Platform is a digital workflow building and extension tool for ServiceNow featuring a number of low-code / no code tools.
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.
Using it in the application support team is worth it as it is capable of carrying a lot of information. But using it for a Service Desk operation might not be of much use as it won't be used up to its full potential and will be costly as compared to other alternatives available in the market.
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.
Providing admins/devs with easier mechanisms for providing businss stakeholders with self-service admin capabilities across the platform
Tutorials on how to be the best at reporting in servicenow
Guided tour functionaltiy is a bit rigid and could use more workflow capabilities
Making it easier to push form variables to the user so there is more context when providing an approval. The out of box approval UI/form is terrible in my opinion.
Everybody in the company is happy to use ServiceNow. All people are happy to use a user-friendly web tool in order to open IT incidents. IT people can easily support people with a stable and solid tool.
As a regular user of the ServiceNow platform, including the incident management, change management and enterprise application management modules, I find that I am able to competently use the platform with minimal training and assistance. User guides are available from the vendor if required. The customisable front-end that we use in the organisation as an ordering tool for internal IT services is very easy to use, and makes searching for the required IT service simple for business users.
We have many levels of interaction with ServiceNow. The first line of support sometimes is not equipped to resolve more complex issues, but the escalation process is clearly defined and followed with limited friction. Our account team is very responsive and willing to brainstorm ideas to improve and increase usage. We also have direct interaction with product teams to see previews of new features and at times to provide input to influence implementation details.
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.
ServiceNow is by far a better tool over Remedy. Its ability to integrate so seamlessly to so many tools allows for plenty of opportunity to streamline and improve processes. Servicenow has intuitive flows that allow you to quickly pivot if process change. Its adaptiveness is what makes it far better solution over Remedy
1. It is not great when they can't seperate apps/products from a particular sku, forcing you to make a business case for a larger portion of functionlity than your current business case seeks to address. 2. ServiceNow reps are able to work with you when economies of scale are projected out. They are willing to start at a desired tier and provide pricing at applicable upgraded tiers
Very easy to use. Capture more data from the Incident and problem management. Easier to escalate and following the change management process to resole the issues.
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.
Ensuring good service support internally and externally has triggered opportunities to sustain good links with everyone and opened the door to more sales and successful business and ServiceNow has been key in all this, so the investment came back to us faster than expected.
