What do you like best?
- A library or function already exists for most any purpose
- Powerful, flexible data handling capabilities
- RAD thanks in part to so many common functions (navigation, security, etc.) being available
- Use of the eclipse IDE
What do you dislike?
Not exactly a "dislike" but 1 issue I had: Builds could take a very long time when connected to legacy data (Visual FoxPro DBF files, using JDBC).
Recommendations to others considering the product
I would definitely recommend using Servoy (both the company and the product) since my own experience has been singularly positive. I think Servoy is especially well-suited to getting a certain kind of legacy app rewritten and up and running. In our case, simply reproducing existing features and functions was always accomplished fairly quickly and efficiently, and the resulting product was also cleaner, more maintainable and more user-friendly - no small feat given the upgrade from FoxPro to a true multitier architecture.
Beyond this general recommendation to someone considering Servoy, I would also suggest two things:
1. Try to do a proof of concept that includes a real business/programming concern (using your own data) since this should provide a good picture of what a larger Servoy project is going to look like.
2. Use Servoy resources to the extent possible, which often saves time & money in the long run despite some upfront cost.
What business problems are you solving with the product? What benefits have you realized?
- Updating a critical legacy application originally written in FoxPro 2.5 and rewritten in Visual FoxPro approximately 15 years ago
- Primary benefits are 1) Servoy expertise & experience, and 2) rapid development