If you’re familiar with Git, you may have heard about Git rebase. This powerful command allows you to attach your Git branch to any location on your Git tree.
However, I have often heard about developers’ disdain for this command. Instead, they favor Git merge — a safer yet limited way to deal with their branch history.
Let’s first illustrate how they differ with a trivial example.
Say you have a base branch called
develop. Imagine you create a branch from
awesome_branch. Meanwhile, someone commits on
Navigating remains one of the most challenging topics in mobile applications. While using navigation components or your own navigator, you’ll find many ways to route to a set of screens.
Nearly all mobile applications include text. It occupies a significant amount of the user interface (UI). This study shows that text content covers 30-40% of some of the most popular iOS apps’ UI.
As a result, you should focus on how readable your text is when conceptualizing your UI.
Let’s take an example. You may want to display some text on top of an image. Have you considered that your text color could merge with the image’s background? If not, chances are your users can’t always read it.
Imagine you’re revisiting an existing feature on your application. Sometimes, it’s such a change from the previous version that you will want to communicate about it. You might want to onboard your users with this updated functionality.
You want to trigger such an event when you’ve shipped this feature. However, notifying users who upgrade your app is all that matters. It brings no value to onboard new users from a revisited experience.
The Android SDK provides no mechanism to distinguish how your users obtained your application. They may have done so by either:
If you’re a mobile developer, you should be familiar with deep links. They bring a navigation mechanism to your application. With them, you can both:
So why are people often confused about them? And why is it so important to be accurate when communicating about deep links?
To answer the first question, I’ll need to explain what deep links are and how they behave. Since there are different types of deep links, you’ll want to dig deeper to clear the confusion.
Git is a powerful versioning tool allowing you to share code with your team. It lets you sandbox your work in a dedicated space called branches. How you manage branches is up to you. What matters is: how do you glue all those branches together when the delivery time comes.
Vincent Driessen presented ten years ago Git Flow. Since then, many developers have adopted it. So massively, that he recently wrote a note in his original post. He thought valuable to urge developers to consider this workflow only if you must deal with several versions in production.
If you fit…
I’ve been using Git for many years, and I’m still far from knowing it all. However, I feel like Git has the answer each time I face a problem. More recently, I’ve been wondering how we could remove the boredom of prefixing commit messages with a Jira ticket number.
I’ve always felt that naming my branches and commit messages was tedious. Despite this fact, I always strive to respect naming conventions. They’re vital to keeping proper versioning and helping your teammates seek your branches.
Creating a website can seem overwhelming. Even with a programming background, you may lose yourself on the web trying to find where to begin.
So here is my promise to you. At the end of the article, you’ll get:
I’ll tease you with the website I recently launched. …
Every Android developer begins their journey by enabling the developer mode on a device. Without this option, you cannot install your application on your phone.
Although this menu can unlock your device for deployment, it also contains many debugging tools. Some day, one of them may pull you out of a dire situation.
So before diving into the code, let’s take a moment and peek at the available tools inside the developer options. I won’t present them all. Instead, I will focus on four that have helped me a lot over the years.
When building a layout, you have countless…
Voice recognition has gained a lot of traction over the past few years. When building an app where you feel speech recognition would boost your user experience, you can either:
SpeechRecognizer in your Android application is straightforward. I’ll provide a detailed implementation later in the article.
However, we want continuous voice recognition. Unfortunately, the API doesn’t provide a mechanism to trigger voice recognition using a keyword. All voice recognition systems are based on this pattern, whether it’s “Ok Google” for Google Assistant, “Hey Siri” for iOS, or “Alexa” for Amazon devices.
Android advocate @Betclic