Systems | Development | Analytics | API | Testing

Apple recently announced that starting from April 25, 2022, all iOS or iPadOS apps you submit to the App Store need to be built with Xcode 13 (or later). This means that Xcode 12 is now deprecated, and people using Xcode 12 or older can no longer publish their apps to the App Store without upgrading their Xcode version. Each year, Apple decides to deprecate the older version of Xcode and stop allowing apps built with it to be uploaded to the store.

In the development world, it’s very common for technologies to be rapidly updated to introduce new features that improve the development experience and performance. These updates are very beneficial for developers because they allow them to create better products. This is especially the case when a CI/CD like Codemagic is used for continuous deployment that streamlines the process of delivering new products.

The term “observability” means many things to many people. A lot of energy has been spent—particularly among vendors offering an observability solution—in trying to define what the term means in one context or another. But instead of getting bogged down in the “what” of observability, I think it’s more valuable to address the “why.” What are we trying to accomplish with observability? What is the end goal?

Finance professionals know that data matters, but stories convey truth in ways that mere numbers simply cannot. Those who work in finance may describe themselves as “numbers people.” They have a natural affinity for quantitative information, as well as a knack for drawing meaningful conclusions when presented with a collection of numerical figures. Even so, finance team members probably understand and retain information more readily when it’s presented in narrative form.

In this article, we are going to explore why the Stripe developer experience is so passionately supported by thousands of developers globally. One of Stripe’s missions is to increase the GDP of the internet, and over the last decade, they’ve successfully executed 250 million API requests per day and over 91 billion requests per year through their APIs.

The Ably Kafka Connector has a raft of new enhancements, and is now available in a full general availability (GA) release. Developers now have the option to use pattern-based mapping rules to enable streaming of data from many Kafka topics to many Ably channels - ideal for chat solutions, live sports updates, live streaming, broadcasting notifications and alerts.

Static sites (websites) are not new. In fact they’ve been around since the era of Web 1.0. Back in those dim and distant days the internet only had a few contributors, so managing and maintaining a static website was fairly hassle-free, they use to have a couple of static html files. However, the needs of creators and consumers have changed dramatically since then. So we need a new technology to generate static sites, befitting the resources and innovative spirit of the digital revolution.

We are going to explore whether Load Test Driven Development is an idea that would be worth pursuing for your organisation. We will recap on what Test-Driven Development (TDD) is in the next section but fundamentally Now when you think about this, does it make sense to try and run a performance test before we have developed any code? We think it does and we are going to explain why. For clarity we are not suggesting that Load test Driven Development should replace TDD but rather to compliment it.

Our new podcast, "The People Behind Your Favorite Apps," shines the spotlight on the developers, testers, and others who work tirelessly to bring amazing technologies to market. How they come up with solutions to big challenges, collaborate at scale, and deal with high-pressure deadlines and increased expectations from the business and customers alike.