Magic xpa Application Platform Pros and Cons

Typically an experienced Magic developer can do the work of two to three experienced C#/.NET developers. Customers are amazed at how quickly most new features can be added and bug fixes implemented. I have worked for four employers - including myself - using Magic, and in most instances, bug fixes are addressed and deployed in under six hours.

Speed of development and database connectivity (MS SQL, Oracle, DB2, Btrieve/Pervasive PSQL, ODBC, MySql, and SQLite).

The ability to use the same development environment for both Windows and Android applications. Magic xpa also supports iOS applications.

Magic is rapid, it's a tool which we use to develop, change and maintain our programs. xpa has a lot more features onboard and it gives us the opportunity to do such things so that we can easily adapt and maintain our programs. It gives certain benefits to stay with our customers and the market.

Being able to make changes to existing programs to comply with last minute changes in requirements, and/or being able to fix, test, review, and deploy new code in a manner of hours instead of days, definitely gives us a huge advantage over our competitors and this is only possible thanks to Magic’s speed of programming.

Magic’s unique approach to development ensures that the programmer stays focused on the objective of the program (i.e. display all customers in California), instead of the repetitive tasks that surround it (i.e. connect to database, open customers table, create the query to retrieve records within the specified criteria, fetch the result of the query, connect it to a data grid, etc.).

Magic’s Database Gateway allows the logic of the program to be isolated from the underlying database. This provides the flexibility not only to move existing programs to different database environments without the need to change the logic in the program but also allows the programmer access to different databases without the need to know how to "talk" to them.

Without the need to compile code, the time spent in the development cycle is greatly reduced, allowing the programmer to test modifications to a program immediately after they have been saved.

The configuration of the xpa RIA mobile environment is complex and a discouragement to new developers. Also, Magic's documentation can be less than complete at times which leads to frustration for new developers. (I encourage new Magic developers to join the Magic Users Group).

The Android environment is missing a number of functions for file/folder manipulation, sending receiving text messages (SMS) and the menuing options are limited. For now, it is left to the developer to write his/her own Java functions to include in the APK.

It is missing basic charting tools for bar/pie/series charts. It is left to the developer to acquire and deploy charting tools or the customer to purchase a third-party reporting tool to produce charts.

I would like to see a spell checker included with optional language support. Currently, this has to be purchased from a third-party.

The ability to display page up, page down, top and bottom buttons along the scroll bar would make my mouse-reliant customers happy.

When you have several tasks, you open a screen in a task in developing mode, and you don't see the parent screens. Debugging lacks the effects to solve problems. You have to do it first in a kind of studio. Then you have to be sure that you can do it in Magic because there is almost nothing to debug it. It's practically impossible to debug. You have to be sure before you put your snippets.

Magic has a tradition, when it adds new technologies/features to the Magic development tool, to provide either no documentation or documentation that does not provide an organized approach for bringing this new technology/feature to experienced Magic programmers.