googlemaps-samples / googlemaps-samples/android-samples
Modernize our Android samples
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 2.5k
- Forks
- 3.1k
- Avg merge
- 3d 54m
- Merged PRs (30d)
- 4
Description
Most of our samples are slightly outdated. We could adopt a more modern approach (using Binding, removing setContentView, improving our permission handling...) and adopt a syntax more in line with Kotlin, for the Kotlin samples.
If you would like to upvote the priority of this issue, please comment below or react on the original post above with 👍 so we can see what is popular when we triage.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inventorying the Android samples, separating the Kotlin samples from the rest and noting which ones use setContentView, older permission handling, or non-idiomatic Kotlin syntax. The issue does not name files or tests, so define the affected sample set and modernization criteria before changing anything; done means the agreed samples consistently use the selected modern approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100