Xamarin development is great for creating cross-platform native mobile applications without duplicating code for each of them. But, for those not using the Apple ecosystem, there’s an issue that can be a barrier to building Xamarin iOS applications.
User Acceptance Testing is a vital but often overlooked aspect of software development. It can seem redundant, and no one wants to hear about software bugs from a frantic email from an end user. But developers and end users may not always have the same understanding of the requirements, and it’s better to know about any potential issues or misalignments before the software goes live rather than afterward.
In this article, I cover some User Acceptance Testing best practices to ensure your application is thoroughly tested, bugs get resolved before launch, and clients are successful and happy.
Recently, I had the pleasure of attending the 2018 DevOps Enterprise Summit (DOES) in Las Vegas. While conferences tend to make me fearful of getting sucked into a big sales show, DOES restored my faith (in the value of conferences, not Vegas!). Notably, it was extremely well-attended, impeccably run, and there was an elite cast of speakers throughout the event. From large talks to small group sessions to book signings, the event offered seemingly endless opportunities for interactive education.
Keeping applications up-to-date is important. It allows you to take advantage of the latest framework/component features as they are released, run on the latest devices/platforms, and provide the best user experience possible. Upgrading from one version to the next is usually easier than jumping two or more versions ahead. For these reasons, regular application maintenance to upgrade frameworks and components as they come out is the preferred approach.
One of the foundational steps in moving to DevOps is application monitoring, which is not always easy. There are many different possible performance problems and limitations, and the only way to track them down is by collecting information in bulk. Ask any developer who has maintained an application without the proper monitoring tools, and you'll probably hear a story or two about some issue that took months to track down or is still plaguing the application. Developers, server admins, and network engineers need information to be able to track down a problem.
In this article, I walk through an example of how application performance monitoring can help quickly discover, isolate, and solve problems that can negatively impact the user experience.