Reviews (1-2 of 2)
December 14, 2018
Score 9 out of 10
We chose it because we need a framework to build rich internet applications especially to build business applications. We also looked for a tool that was very well established in the market with the first version released more than 10 years ago. We also didn't want to change the framework periodically.
Read Gonzalo Segarra's full review
It's great to develop business applications. Previously, we tried different technologies but we find it the most suitable for us. We also deploy a generic backend so we don't need to install anything new to implement new applications. This helps us to develop very fast and with very low effort.
August 31, 2016
Score 8 out of 10
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.
Read Abraham Madathil's full review
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