This article highlights three technologies that you can combine to create a super-app: Flutter, Firebase, and Codemagic. Our task is to configure Firebase for all platforms supported by the Flutter framework, utilize Firebase Remote Config to alter the appearance of our app without making these changes manually and then set up CI/CD using Codemagic to distribute our app via Firebase App Distribution. We’ll be creating a live demo of the app to demonstrate the power of these technologies.

While the prospect of getting much faster build times with the Apple silicon (aka M1) processors seems very exciting, you may face issues that stem from the architectural differences between arm64 and x86. One of these issues is related to snapshot testing or golden testing on Flutter. You are not alone in this, as it’s a widespread issue in which snapshots generated on an Intel machine fail on Apple silicon machines — and vice versa.

After you successfully build and test your app, you may want to upload the build to TestFlight or the App Store. Sometimes, you may face an unknown authentication error that makes it difficult for you to upload the iOS binary to App Store Connect. You may even face an authentication error after using a valid App Store API key. If you’ve faced this problem, you’re not alone.

Have you ever faced the task of implementing a REST API and had to call multiple endpoints to populate data for a single screen? You probably wished you had more control over the data returned by the endpoint so that you could fetch more data with a single endpoint call or have only the necessary data fields returned by the call. Follow along to see how you can achieve this with GraphQL. In this article, we’ll be implementing GraphQL in an existing codebase.

As the size of a software project grows, so does the complexity of integrating changes made by multiple developers and resolving conflicts and other issues as they arise. Quality control can also become progressively more difficult without proper management of the build pipeline. Automated builds are the standard solution to this problem across the industry. Understanding build automation in detail is a valuable skill for any developer, no matter the size of their team.

TL;DR: To add events monitoring with Crashlytics to a Unity Android app, you’ll first need to prepare a Firebase project, then add the Firebase plugin to Unity and configure Unity to work with Firebase. Finally, you also need to update your CI/CD pipeline to support the changes. Let’s see how to integrate Firebase Crashlytics into a Unity Android app to monitor and troubleshoot errors easily!

Navigation is a core concept in mobile app development. It enables users to move from one screen to another. Well-managed navigation keeps your app organized and enhances its capabilities. Flutter offers an imperative API (Navigator 1.0) and a declarative API (Navigator 2.0) routing mechanism. In Navigator 1.0, you can only add a page to the top of the navigation stack and remove the topmost route. On the other hand, the declarative mechanism allows you to control the navigation stack completely.

As you may have noticed from our blog, we’ve been talking a lot about Unity lately. Obviously, this is for a reason. And now I can officially say that Codemagic supports Unity CI/CD. What’s more, it’s publicly available — you can try it out right now! Try Unity CI/CD now! For those of you who are still reading, let me tell you a story.

Are you about to start your next mobile app project and can’t decide whether you should use Flutter or native languages? If yes, then this article is for you. Stefan Ionescu focuses in this article on the differences between Flutter vs native development from different perspectives.

As an Apple platforms developer, you have surely come across a scenario in which you have had to create new screenshots for App Store Connect while releasing a new version. The designer may have given you the screenshots beforehand, or maybe you have manually opened the corresponding simulators and taken the screenshots yourself. You must upload a minimum of three screenshots for each of the four devices on App Store Connect. That is a minimum of 12 screenshots per release.