Overall Satisfaction with Sencha
Sencha is currently being used by pretty much my whole department. Some basic feature that attracted the org to adopt sencha were:
- It's a complete solution - no more figuring out solutions from 10 different places
- They have a support model in place in case one hits road blocks
- It would be easy to build on mobile platforms as it's already embedded into the framework
- It's a complete solution that has a vast array of pre built components, charts and a data-grid based solution.
- Security comes out of the box.
- It's mobile and tablet ready.
- It has a lot of support from the community so solutions are easily available
- You can add your own flavor via theme customizations and built in component extension.
- Changing some implementation of a component already defined is not straightforward, it needs a lot of understanding.
- It takes a fair amount of time to even get the basic shell of the application up and running if you are starting from scratch.
- It's very expensive from a licensing cost point of view.
- Developers are more focussed on implementing the business logic as compared to figuring out technical challenges of some slick user interface component.
- Business is happy with the ease of use introduced by the new UI components.
- We are well placed to move our application off from a purely web based platform to a mobile and tablet based solution.
- bootstrap, AngularJS, Kendo UI and KnockoutJS
Each of the above platforms offer a specific solution. Sencha provides a complete solution that is a library of components as well as a framework to modularize your application so that it's better manageable. Once you get over the learning curve of the whole technology it's a breeze to implement new functionality within the application. We have an aggressive client who comes to us every other day with some new requirement, and sencha has been able to answer all of those without issues.
Sencha is suited for:
It's not uited for:
- Enterprise applications that are really huge
- Development happens on huge teams, on-shore an offshore model, one can divide and conquer by splitting in modules easily
- Budget is not a constraint
It's not uited for:
- Small budget applications
- Not too many components are needed
- Static or less dynamic content based websites
- Turnaround time is shorter and developers have to spin something around in a short duration of time