I started the Flutter challenge hosted by Nomad Coders last week.
Since Flutter uses the Dart programming language, I began by studying Dart.
One of the most fascinating aspects of learning Dart was the variety of compilers, and most of the syntax seems to be similar to that of modern programming languages.
This week, I completed lectures on Dart features, variables, data types, functions, and classes.
The focus of the lectures seemed to be on a level sufficient for using Flutter rather than covering every aspect of the Dart language.
When programming languages or libraries are updated, or when new code is written, I need to develop the habit of closely examining the existing code (legacy) that could be impacted.
For mobile apps, services that inform us of the reasons behind crashes are typically represented by Firebase Crashlytics.
Firebase Crashlytics is free and seems to be a decent choice within the mobile category. However, Sentry is also a great tool for logging crashes on the server.
Upon reviewing Sentry, I found that it offers a wide variety of options, including detailed reasons for crashes, screenshots at the time of the crash, and correlations with views.
What is Firebase App Distribution? It is a service that allows you to distribute app files and download and test the app using that service. It is similar to Apple’s TestFlight, but since Android cannot use TestFlight, App Distribution is available for both Android and iOS.
To use it on iOS, you must download the AppTester app. However, you cannot download the app directly; it is available via a website shortcut. My impression of using it on iOS is that the speed seems faster than TestFlight, but it appears to have a complex initial setup involving profile settings and device registrations. Therefore, for projects that do not plan to distribute on Android, I think I will often prefer the more accessible TestFlight.
I modified the deployment task using the Slack Slash command I created two weeks ago to trigger the Bitbucket pipeline with Jenkins, so I studied Jenkins. However, to run the pipeline in Jenkins, the machine must be a Mac.