Opiniones de Essential Studio

Es un producto fácil de utilizar, y se adapta rápido a los proyectos que estamos desarrollando

el tiempo de respuesta de los Bug, que se basen a los votos para atenderlos.

You can find always a control for all your needs and it's also easy to use.
With this software you can implement features in seconds, that otherwise would require a good amount of time.

There isn't much to say about cons, because there aren't cons really.

Not like other software, I got it fully functional with licence softer with full featured and professional look components. Which helps me to develop a professional and rich ui software

Nothing like that. Blazor is still not released from Microsoft. So features might be enhanced. However I am getting full support when I stuck with issue.

Our project is to build a commercial-grade, security-compliant, serverless mobile app platform using only tools that are budget-friendly for startups. Our tool-chain selection includes AWS services (API Gateway, Cognito, Lambda, DynamoDB, ...), Microsoft .NET Core/Standard, Visual Studio and Xamarin. All these tools are essentially free until your app starts scaling. Syncfusion's community edition was chosen because it provides commercial-grade features and doesn't burden the entrepreneur with out-of-pocket expenses until their app is generating revenue. Finally, our experience with Syncfusion's support has been first rate.

Syncfusion targets many different UI presentation layers. In our case, we use Xamarin Forms which is relatively new for Syncfusion. The controls are generally solid but do require more "code-behind" work than is generally recommended in the Xamarin community. There are shops that totally refuse to allow "any" code-behind and if you are one of those you may have some issues using all of the Syncfusion controls. In our case, the limited code-behind required is not considered a barrier. In addition, the Syncfusion documentation is obviously not written by a native English speaker and as such can be amusing at times and occasionally annoying .

Richness and completeness of controls and good and quick support.

Examples in the github non always complete and clear, poor availability of code snippets.

Diversified features of the grid - has almost everything I needed from a grid.

Learning curve is steep as there are a lot of small tweaks one should know in order to achieve something.

Conversion of word docs to pdf with ease

Having to obtain a new key for every version and/or bug fix
Conversion of word doc to pdf was buggy at first - tables were not converted properly

It’s components provide many built in features, which makes the development easier. The support team is another plus. They are just great.

Community forum is a little hard to use.

Due to the comprehensive Online Documentation and User Forum, the first and basic steps are easy to accomplish.

When updating to newer versions and/or updates it is very important that you follow the exact steps, as described in the corresponding documents. Otherwise you will end up in a situation where your app does no longer compile and run.

the support team one of the best we work with them very fast.

take time to learn to use it's not straightforward. first two months you need contact to support a lot.but the support team one of the best we work with them very fast.

Integration with our business processes was easy.

Some of the features differ from how they are entered or set within the actual application such as Excel and PowerPoint. And some of the features that I require in order to produce the desired output are not present.

Six years ago, I started developing a large scale enterprise product. It required a lot of full stack development. It runs on Windows, Android and IOS. The infrastructures is all Docker containers. I am not a UI guy and didn’t have the time to build the UI components needed. Syncfusion components work well. Their generous licensing policies made using the tools possible.

Most impressive, is that I have received the same quality support as one of their paying customers. My system has architecture that I developed to solve a problem specific to my target industry. I did hit a bug that had not been seen before. Syncfusion’s support staff verified that the bug was in their code and issued a patch without argument. I can’t tell you how many times a company has told me “the software is not supposed to do that, so it’s not a bug”.

There are components that I found difficult to understand even after reading the doc. But it was more the task at hand then a problem with a component. For example: To use the Word functions to manipulate a Word file, you must understand how Word structures its documents. But a note to support always results in a sample. So, really there is nothing negative to say.

It works, renders html correctly enough.

Non-platform independence for devops - requires package installation on deployment targets. Also requires manual setting of path to syncfusion binaries (that are in the nuget package!) at runtime.

Extra package e.g. Syncfusion.HtmlToPdf.Blink.Static.Linux could be created with a static compile to eliminate system dependencies and manage CVEs etc.

The code (which we have had to write ourselves) to locate the native binaries originating from the nuget package should be inside the syncfusion lib - there should be no argument to their path.

Also, while it might bloat the package, nuget supports separate native binaries per runtime [SENSITIVE CONTENT HIDDEN] which would enable to create a single platform-independant nuget package - this would really lower the difficulty - especially in places like dotnet-script where you have no csproj to change the PackageReferences depending on the runtime!

Great set of Tools! But equally important I would say is the stellar support that you receive. ES also has a huge community so I've rarely had to reach out for support as there is usually documentation on whatever issue I am currently having already.

However I have been amazed that such a Enterprise Level company has a support team that actually gets back to you in a day or two with either code examples or a resolution! In my whole development career of over 15 years, I've never seen that level of dedicated support! Not from Microsoft, Google( Does Google even do support?) or any third party tool.

Integration into projects isn't bad... I just wish it was a little more streamlined especially into Visual Studio. I ended up going with the Nuget Package installation because the other proved to be buggy and problematic.

This products solves almost all our needs along with the standard ui and productivity components on the platforms that we deliver solutions on. We are almost entirely an angular/typescript, asp.net core and Xamarin shop.

Sometimes the documentation and examples leave something to be desired but the very quick and responsive customer support more than compensates for that.

The good documentation, many samples, easy to apply on our software, but most of all the outstanding support from the company that supplies a sample to solve a problem or any How To question. Is very attentive when a possible bug is pointed out and if it is a bug a fix is provided in a scheduled time.

the only thing I don't like much is that upgrading the desktop projects when I upgrade the libraries is a time consuming task. But I don't think there is a way to avoid this.

+ Complete suite of UI controls for .NET and Xamarin.Forms. Also its includes report, pdf and others libraries. No other library is needed.
+ Support is great. Generally they bring a one week solution when an issue if found or a quick workaround.
+ Many samples and Documentation available.
+ Grid is great.

Sometimes there are some specific functionalities that we wanted but with some extra work we can cover them.

We use 10+ different Syncfusion controls from Essential Studio for Xamarin and they quite literally have become an Essential part of our mobile product. They allow us to provide a UI with much greater polish and depth of functionality than the stock Xamarin Forms components while maintaining all of the cross-platform benefits between iOS and Android. And the Syncfusion support has been stellar. They have gone above and beyond on multiple occasions to help us track down obscure issues, some of which ended-up being our fault. Very highly recommended!

Event handling in some of the components can be challenging to work with, and some of the components have some annoying quirks, but these are minor quibbles overall. The written documentation can be difficult to read in places, but at least they do have extensive documentation.

It is easy to implement and good support

Not easy to what you are looking for in documentation

The span of features is impressive, and when operated out-of-the-box everything "works". Once past the licensing issues, it is easy to use within an application for normal, simple features and feature set combinations.

The documentation detailed how to implement several features for the Grid control. However, using the features resulted in unstable and inconsistent behavior in the UI. Working directly with support/development programmers from Syncfusion, found that there were several issues with timing within the control code and how to access the control API that were not documented. The result from the developer sessions was more complicated and very dissimilar to the published documentation for these features, but it finally started to work consistently.

I have been using Telerik's controls for almost 10 years now before being introduced to SyncFusion.

I would have to say that the Community License is the greatest reason for me to switch from Telerik.

Currently I am working on Angular projects and I have only used SyncFusion's Angular controls but I have found that the controls are equal to or greater in quality to the Telerik controls.

The grid in particular is much easier to use and develop with; it has been a challenging learning curve to transition from the Telerik grid control only because I have had to map actions and events from one to the other.

I think if I did not have such a long history with the Telerik controls, I wouldn't have any issues in learning to use the SyncFusion controls. I found this to be true when working with controls I had not used before .

Other than issues transitioning code from Telerik to Syncfusion, I haven't found any cons for using SyncFusion.

Great product and if you ever need any assistance their support is awesome.

We *do* occasionally run across bugs or broken features

Syncfusion controls whether for the Web or any other platform are well built, well documented, and well supported. All three of these points are extremely vital to project success.

The thing is, if I ever have an issue, I get ahold of online support and they help us out right away. They always help me find the correct way to use a control, and give me a sample to help the process along. In some cases, they will even update their own code to support a feature I think is important.

The components at first looks like they have plenty of functionality. If you are fine by using them in read only mode (no interaction needed) they might be very useful to you. They look good to the user, have localisation support etc.

Buggy components. Implementation requires a lot more code than similar components on the market. E.g you had to specify TItem type explicitly for grids and comboboxes. If not given the components fail to load on empty data resulting in Blazor app crash.

We decided to switch to Devexpress.

Pretty easy to use the controls, and also many options in customizing and extending them.

Too many bugs in almost every control that we've used. Exception handling is missing in many critical points that causes many - many application crashes.
Each time a new release came out and we've decided to upgrade, new bugs came out. It seems like the controls are never tested in real life complex scenarios but only in demo examples that use very basic options.
At very least, even if a bug appears a error should be thrown in the UI instead of terminating the whole application that leads in bad user experience.