Senior Software Engineer at Denso Ten Solutions Philippines Corporation
Real User
Top 10
2023-01-27T10:33:06Z
Jan 27, 2023
Throughout my career, I've encountered difficulties when integrating new technologies with Magic xpa Application Platform. In particular, when attempting to incorporate features from other development languages into earlier versions of the solution called uniPaaS. I struggled to integrate .NET components due to the limited options available. This made the process more challenging and complicated. I find it challenging to create a more user-friendly experience for users who may be comparing the system to other systems they have used outside or within the company on different platforms. Currently, I have encountered an issue as I am engaged in mobile development utilizing the Magic xpa Application Platform. The process of releasing on iOS is more complex compared to Android, and in future iterations of the solution, the integration of the iOS platform would be of great advantage. This is because when it comes to deployment, the procedure is more demanding in the case of iOS compared to Android.
Senior Associate - IT at Himalaya Wellness Company
Real User
Top 10
2022-12-16T11:34:00Z
Dec 16, 2022
It's a bit difficult to work with purely web-based applications to get the data and display it. There have been a few times when the connection was disconnected between the server and your browser. The connectivity on browser-built applications needs to be improved. The mobile application development could be easier. They could include different external applications, like finger sensors. I'm not sure whether it's in version 3.8 or not.
There is room for improvement in Magic's marketing and licensing. If you talk to people about Magic, there is a pretty big chance that no one's ever heard about it. It's not mainstream like .NET or Java, and that's because of the marketing and licensing strategy of the company. They never put an emphasis on marketing, so now it's unknown. When programmers first came into contact with Magic, they saw the benefits, but they had to pay for a development license or a one-time license. I think that's the main disadvantage of Magic because that's a big threshold preventing Magic from being a mainstream competitor among Java and .NET. As for new features, I would like to see more integration of web functionality. Client-side intelligence, rather than service-side, and done in an easy way. It's already possible, but there is still some work for you to do as the developer. The most standard functions could be automated a bit more.
The solution is complex and has a long learning curve. I am not referring to its initial setup, which is very simple, but its use. Support is very bad. The main focus is placed on their own customers, big banks and big insurance companies, so those, like us, who are independent software vendors, are ignored. While I have tentative, though not definite, plans to increase the usage, the solution suffers from certain weaknesses, such as its essential lack of an internet web interface, a feature I really want. I rate the solution as a nine out of ten, since everything about it is good, save for the internet connectivity. Everything having to do with the internet is underperformed, which is not good. This is my main issue with the solution. The licensing is too costly. The runtime cost is very expensive, especially in respect of a big server with many clients. So too, the development tool is expensive, as is the yearly maintenance cost. While the solution is perfect for one who wishes to make local, standalone solutions on a Windows network or computer with an Oracle database, it is not well suited for internet-or-cloud-based distributed systems.
CEO at a tech services company with 11-50 employees
Real User
2019-11-13T05:28:00Z
Nov 13, 2019
The company has now released version 4 for web development. But this new release is still pretty hard to use for mobile and web development because it was not improved as much as we expected in the areas of user-friendliness or development-friendliness. In general, the interface is okay, but to achieve a final result, it is not very friendly for developers. It could be improved by adding services that can be automated. This will be a major improvement in functionality.
When you have several tasks, you open a screen in a subtask in developing mode, then you don't see the parent screens. Debugging .NET snippets is not possible, so it lacks the effects to solve problems. First you have to write and test your .NET code in VS. Then you have to copy the .NET code in Magic XPA because there is almost nothing to debug it.
Learn what your peers think about Magic xpa Application Platform. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
Magic xpa Application Platform is a mobile development platform that is designed to enable organizations to simplify and manage every aspect of their application development process. It enables users to construct applications while expending a minimal number of resources. Developers can leverage AI technology in a way that maximizes their ability to effectively deploy their resources toward the end of producing the best possible applications. Ultimately, Magic xpa Application Platform allows...
Throughout my career, I've encountered difficulties when integrating new technologies with Magic xpa Application Platform. In particular, when attempting to incorporate features from other development languages into earlier versions of the solution called uniPaaS. I struggled to integrate .NET components due to the limited options available. This made the process more challenging and complicated. I find it challenging to create a more user-friendly experience for users who may be comparing the system to other systems they have used outside or within the company on different platforms. Currently, I have encountered an issue as I am engaged in mobile development utilizing the Magic xpa Application Platform. The process of releasing on iOS is more complex compared to Android, and in future iterations of the solution, the integration of the iOS platform would be of great advantage. This is because when it comes to deployment, the procedure is more demanding in the case of iOS compared to Android.
It's a bit difficult to work with purely web-based applications to get the data and display it. There have been a few times when the connection was disconnected between the server and your browser. The connectivity on browser-built applications needs to be improved. The mobile application development could be easier. They could include different external applications, like finger sensors. I'm not sure whether it's in version 3.8 or not.
There is room for improvement in Magic's marketing and licensing. If you talk to people about Magic, there is a pretty big chance that no one's ever heard about it. It's not mainstream like .NET or Java, and that's because of the marketing and licensing strategy of the company. They never put an emphasis on marketing, so now it's unknown. When programmers first came into contact with Magic, they saw the benefits, but they had to pay for a development license or a one-time license. I think that's the main disadvantage of Magic because that's a big threshold preventing Magic from being a mainstream competitor among Java and .NET. As for new features, I would like to see more integration of web functionality. Client-side intelligence, rather than service-side, and done in an easy way. It's already possible, but there is still some work for you to do as the developer. The most standard functions could be automated a bit more.
The solution is complex and has a long learning curve. I am not referring to its initial setup, which is very simple, but its use. Support is very bad. The main focus is placed on their own customers, big banks and big insurance companies, so those, like us, who are independent software vendors, are ignored. While I have tentative, though not definite, plans to increase the usage, the solution suffers from certain weaknesses, such as its essential lack of an internet web interface, a feature I really want. I rate the solution as a nine out of ten, since everything about it is good, save for the internet connectivity. Everything having to do with the internet is underperformed, which is not good. This is my main issue with the solution. The licensing is too costly. The runtime cost is very expensive, especially in respect of a big server with many clients. So too, the development tool is expensive, as is the yearly maintenance cost. While the solution is perfect for one who wishes to make local, standalone solutions on a Windows network or computer with an Oracle database, it is not well suited for internet-or-cloud-based distributed systems.
The company has now released version 4 for web development. But this new release is still pretty hard to use for mobile and web development because it was not improved as much as we expected in the areas of user-friendliness or development-friendliness. In general, the interface is okay, but to achieve a final result, it is not very friendly for developers. It could be improved by adding services that can be automated. This will be a major improvement in functionality.
When you have several tasks, you open a screen in a subtask in developing mode, then you don't see the parent screens. Debugging .NET snippets is not possible, so it lacks the effects to solve problems. First you have to write and test your .NET code in VS. Then you have to copy the .NET code in Magic XPA because there is almost nothing to debug it.