Adobe AIR vs. ASP.NET vs. Entity Developer

I would recommend [Adobe AIR] because it works very well, I just wish there were more resources out there on it to help the onboarding.

Incentivized

Well suited: for interfaces between machines data and applications. Made as a service. For web applications in factories where you don't have access to thick clients due to the environment. not well suited: quick measurements and fast data transitions between different applications. When time dependency is needed, then you better can choose other solutions.

Incentivized

• Adobe AIR supports a lot of commonly needed features for mobile app development.
• It is fairly stable and consistent once you learn how to use it.
• It is cross-platform and is supported by some useful third-party plugins.

Incentivized

• It has a great documentation so new or experienced, you appreciate quick access to quality information
• It’s very fast, uses less memory than initially expected that has decreased our costs after moving from python
• It speaks the language of the design patterns really well, so our backend apps are written fast together and connect to frontend systems flawlessly

Incentivized

• Over the course of months/years, various security exploits and other issues are discovered and patched in AIR, often requiring you to rebuild and resubmit mobile apps to the various storefronts. This happens often enough that it's worth mentioning as a major con.
• While development on Adobe AIR seems to be fairly constant, there is very little communication between the community and Adobe regarding the future and general support of AIR. The track record of Flash (and particularly Flash Mobile) does not inspire much confidence that Adobe intends to support Flash/AIR for years to come.
• Adobe AIR does not seem to perform as well (in terms of raw performance, memory usage, framerates, responsiveness, etc.) as other hybrid solutions for certain tasks. For example using shaders tends to be experimental still, and graphic/animation intensive projects often require the use of third party frameworks such as Starling.

Incentivized

• Net is just like plug and play, we have to focus on a logic of code rest part can be handled by ASP. Net framework.
• It's a best for only web development.
• One downside with ASP.NET is its reliance on the .NET framework.

Incentivized

It is the backbone of all our products

Incentivized

Although Adobe AIR is just an SDK without an actual "UI" it's commonly used within Flash, Flash Builder, or FlashDevelop. Considering the integration with Flash IDE, there are very few tools that can compete with its features.

Incentivized

Very good, depending on the requirement and budget.

Incentivized

Originally, Adobe AIR was the only game in town, and its blend of flexibility in platforms it could publish to (PC, Mac, iOS, Android), ease of use, and familiarity made it the clear choice. Now Adobe no longer supports it, and we’ve found the transition to Harmon unworkable for us.

Incentivized

We choose ASP.NET because our core business is working with the SAP HANA database using SAP Business One. We can develop state-of-the-art applications with Razor and Visual Studio 2022 fast and with excellent application performance response. Working SAP Hana with JAVA could be more challenging because it has fewer developers communities, and it could be harder to find a solution for a question.

Incentivized

• Allows easy porting of functionality and look and feel to many diverse platforms.
• Shorten development and deployment time.
• Reduced training and support costs by re-using common widgets.

Incentivized

• We realized positive returns due to interns and new employees already having experience due to the free academic versions available.
• Being able to evaluate the express version prior to purchase was helpful.
• Performance is adequate, but not as responsive as C++. I guess the trade-off is ease of use and being able to find qualified personnel.

Incentivized