Adding some thoughts over Lee's suggestions:

1. **Resources**: Android development is vast and fragmented. For a long time, Google has kept introducing new things and deprecating existing things. There are tons of content on the web, but I would recommend some hands-on with the [Google codelabs](https://developer.android.com/get-started/codelabs?text=java) starting with something [like this](https://developer.android.com/codelabs/build-your-first-android-app?hl=en#0). After this, you can start to have a look at your company's codebase to understand the common Views like ConstraintLayout, lifecycle handling, architecture components, networking etc.
2. **Iterate**: Android development is notorious in the sense that you need to handle a lot of things which may not come naturally. Like user rotates the screen (called configuration change), ideally there shouldn't be anything for the developer to do but you have to persist data and it isn't trivial. Get started with codelabs or small tasks and iterate on it. Learning all at once might be an overkill.
3. **Physical Device**: Android Emulator works just fine but can heat up the system and hamper the performance. Considering this fact + Android builds taking a lot of RAM, using a physical device for testing can provide significant speed boost.
4. **Use Github Copilot**: It can provide some productivity boost where the operation seems trivial like iterating over the list, creating a TextView, creating an adapter etc. You can simply comment your ask like the following. It will generate the boilerplate code which would save some time. It may not work in every scenario but worth giving a try.

```
// create a RecyclerView adapter
class Adapter: RecyclerView.Adapter<RecyclerView.ViewHolder>() {

  protected fun getView(@LayoutRes layoutId: Int, parent: ViewGroup): View {
     return LayoutInflater.from(parent.context)
                          .inflate(layoutId, parent, false)
  }
}
```

Is your company/team moving to Kotlin? As Rahul also mentioned, it's definitely a better choice for developers. If your team is aligned and you will be doing Android development in the long term, you can start with Kotlin as well.

Sr. Software Engineer at LinkedIn

Paras Sidhu

**Fails:**

- I am trying to disambiguate a big project. While I brought a lot new discoveries, I was not able to make enough progress on one core exploration.

**Success:**

- Worked out for 4 days this week (target is 5 days but considering 4 also as success).
- For the discoveries I brought from the project I mentioned above, I was able to dig a bit deeper and come up with multiple proposals. This helped the team to not stay blocked and make progress.