Share your experience using Adobe Experience Manager Mobile [EOL]

We use the product to build Android, iOS, and Windows mobile applications.

The most valuable feature of Xamarin is its testing capabilities. Testing saves both time and cost in mobile application development. The process is costly and time-consuming when developing separate platform-specific applications for Android and iOS. However, Xamarin offers cross-platform functionality, allowing developers to write code once and deploy it across multiple platforms.

Regarding improvements, there are still some limitations with Xamarin, particularly regarding access to core functionality in Android and iOS. When developers need to utilize certain core features of these platforms, they encounter difficulties accessing them directly within the Xamarin project. Instead, they must create and implement interfaces in platform-specific code to access.

We have been using Xamarin Platform for a year.

In my company, only two developers, including myself, are currently using Xamarin.

The initial setup process was straightforward. We downloaded the Xamarin installer and proceeded with the installation.

The product is inexpensive.

The platform is easy to learn as many tutorials are available on YouTube. Additionally, many Microsoft MVPs offer demos and resources that simplify the learning process.

When deciding on a mobile application development framework, it's essential to consider your specific requirements. Evaluate the pros and cons of each available option, including alternatives. The choice ultimately depends on how well the technology aligns with your project needs and your comfort level with learning and adapting to new tools.

I rate it a 9 out of 10.

We use Azure App Service for both app development and deployment. Sometimes, we use it for testing, and we also have several products running in production on the platform.

One valuable feature of Azure App Service for us is its integration with Azure DevOps, which we heavily rely on in our development process. It is user-friendly once you understand how it works, although getting to that point can be a challenge. Additionally, Azure App Service offers excellent integration with Microsoft infrastructure and developer solutions.

In terms of improvement, the technical support could be better.

I have been working with Microsoft Azure App Service for almost six years.

We have faced reliability issues due to configuration issues on our end, not the technology itself. While Azure App Service provides information on problems, sometimes it is not sufficient, and resolving issues can be time-consuming.

In terms of scalability, we haven't encountered any issues with Azure App Service. 

The support I have received, mostly from individuals in India, hasn't been very helpful. They tend to send long emails with lots of links, which often don't directly address my specific issue. This can be frustrating and time-consuming, as it doesn't efficiently solve the problem at hand. Azure App Service might offer better support with higher-priced plans, but those might be too costly for smaller external companies like ours. I would rate the support as a three out of ten.

Negative

I have used SolarWinds along with Azure App Service for web application development.

Installing Azure App Service has been challenging at times. Whether deploying through Azure pipelines or directly from Azure, the process can be time-consuming due to configuration complexities. We have encountered instances where resolving issues took days or even two to three weeks to complete the deployment.

Microsoft offers various pricing plans and licensing options, which initially seem reasonable, especially for small companies like ours. However, as we grow, the pricing can become less flexible. We pay for Azure monthly, while some licenses, like the Action Pack, are paid annually.

Overall, I would rate Azure App Service as an eight out of ten. It is a good tool but could be more user-friendly.