After a long journey in iOS native stack development, my recent incoming projects will be leaning back to Android side again (previously before I started working on iOS in recent years, I’ve been working on Android for around 3 years). After a roughly going through the contents in google’s official Android developer portal, it is a very instinctive thing for a developer with a similar background like me to come out the idea of making a comparison on the two platforms.

By having a systematically comparison of the two platform, one can understand clearly about the difference and similarities of the two and hence, become easier to memorize and handle the development techniques on both of them.

Since the knowledge map of Android and iOS developement contains a long list of topics, which might include for example: OS Characters, Language, Architecture Components, Engineering Tools & Automations, Challenges and Advantages, and etc. When I was writing this article, I was planning to have several post as a series to cover this. In this post, I would like to start with the comparison from the language aspect.

This article provides a summary on Android gradle plugin core use cases and talks about how the Android gradle plugin works via reading through the source code.

Touch event propagation and UI responder chain is one of the most frequently visited topics during iOS interviews. As there are some of the most critical concepts in this topic which can prove whether the candidate have a solid understanding regarding event and gesture detections. A summary is made in this article to discuss:

1. how touch event propagates and gestures get recognized.
2. how UIResponder is relevant to this process.

This article provides a summary on the Swift optional mechanism, the source code of Swift optional can be retrieved here

@frozen
public enum Optional<Wrapped>: ExpressibleByNilLiteral {
  // The compiler has special knowledge of Optional<Wrapped>, including the fact
  // that it is an `enum` with cases named `none` and `some`.
  /// The absence of a value.

  case none
  case some(Wrapped)

After read through the codes, there are some critical knowledge which is essential to construct the implementation

Comparison for frontend backbone design patterns: Flux, Redux, Vuex. Since Redux is commonly know as a replacement for Flux(declared event in its official website) and the development of Vuex has taken a lot of reference from Redux, so in the overall usecases, they are very similar.

In this article, I went through all the integration documents of the three and made a short summary on each of the frameworks core concepts.

Summary for a common UITableView design pattern to support the following cases:

The reason I am writing this is sometimes(quite a lot of times) people are using the term: team leader to provide an ambiguous reference to the job scopes relevant to an engineering manager or a tech lead. But in the meanwhile, there are huge difference between the two….so when the manager is coming and asking he is looking forward you to be a team leader, feel free to use the job scope below to align with him 😂

Just like food and beverages or the any other things which have an expiry date, code also expires and rottens as features keep stacking onto the existing project, which results in a large amount of redundant, ad-hoc, buggy work in the workspace and eventually increases the cost of maintenance for both new feature development and bug fixes.