Systems | Development | Analytics | API | Testing

If you've ever found yourself tangled up in the complexities of setting up CI/CD pipelines, you're familiar with the challenge of mapping code events with build triggers. At times, you may wish to initiate a few checks, while at other times, you prefer to execute several checks at once. It can be slow and, at times, frustrating to ensure that only those CI checks are triggered that are relevant to the code change. A better, more scalable approach? Target-based triggering.

Mobile data provides the eyes and ears of a modern business. It helps us understand where our audience is, what they want to know and what they respond to most enthusiastically. And it can make our apps run faster, too. In a world of ever-increasing consumer choice, this kind of stuff doesn’t just matter. It’s crucial. However, while mobile data can lead to new ideas, it can also be very dangerous if not used properly.

Over 4000 engineering teams are building mobile apps and related projects using Bitrise. One trend we’ve observed is the increasing use of monorepos by some organizations. In this blog, I’ll show you an example setup that demonstrates the current best practice for using Bitrise CI with monorepos. You can use this as a reference for your own monorepo to achieve a CI setup that prioritizes efficiency, autonomy of project teams, and effective governance.

Jetpack Compose (sometimes mistakenly called Android Compose) is a powerful new UI toolkit for Android that embodies the principle of ‘Code As UI’, offering aa simpler and faster way to build native android UI using a declarative approach. Of all the UI components in Jetpack Compose, buttons have a special place, as these are the cornerstone of our user interface. They allow the user to take actions, submit forms, and navigate around the app smoothly.

What it means to be a fan is changing. Whether the fandom focuses on a sports team, a streaming drama series, or a musical artist, fans no longer want to be passive consumers. Instead, they’re looking to feel as though they are a part of the action through channels such as live chat, realtime stats, and behind the scenes insights. But there’s a tension in delivering those fan engagement experiences. Without the right strategy, technology costs can quickly make them economically unviable.

APIs power complex and modern applications and in doing so they’ve also become a challenge to observe, monitor, and analyze. Even the apps we rely on daily consists of numerous services, each glued together by dedicated APIs that interact with one another in intricate ways. In today’s market, you have to make sure that API complexity doesn’t hurt the visibility you need to possess into your product.

Artificial intelligence has become a driving force behind modern innovation, helping businesses across all industries optimize processes and generate income. But how do you monetize AI usage effectively? Whether you’re integrating AI features into an existing plan or launching entirely new AI products, choosing the right approach can unlock steady revenue growth and strengthen competitive advantage.

Kong Gateway offers a fast, scalable, robust, and modular API gateway for your application programming interfaces (APIs), irrespective of your cloud architecture. Kong Konnect adds more benefits on top of Kong Gateway by providing a centralized platform to manage your gateways. However, even with such a powerful platform, you’ll face challenges in achieving that benchmark of API observability and monitoring to meet modern industry standards and therefore your growth projections.

While there were plenty of exciting changes that shipped with Rails 7, asynchronous querying has by far been one of the most talked about features. This is because asynchronous queries can drastically improve the performance of your application by executing long-running queries or complex queries in the background. To better understand why and how this works, let's start by digging into the core of what a Rails async query is.