Use Kotlin Generics

Use Kotlin Generics is not a checkbox topic. It changes how you build, inspect, or reason about a Kotlin Android application. This lesson approaches it as documentation you can work from: first the behavior, then the mechanics, then a reproducible example, and finally the failure cases that matter when the example leaves a tutorial.

In this lesson

• Place Kotlin Generics in the context of the Kotlin Foundations for Android module rather than treating it as an isolated feature.
• Build a mental model for what happens before, during, and after the operation.
• Work through a reproducible example connected to the scenario: build a small Compose-based application with navigation, state, persistence and networking.
• Inspect the result and distinguish evidence from assumption.
• Recognize failure modes, misleading shortcuts, and production constraints.
• Leave with a verification checklist and a practical exercise rather than a memorized snippet.

Where to go next

For a Android developer, Kotlin Generics becomes useful when it changes a decision you can verify. At the beginner stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. In this lesson's Kotlin Generics example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Kotlin Foundations for Android exercise changes the conditions.

The practical question behind use kotlin generics is not simply whether the feature exists, but what behavior it gives you control over. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. In this lesson's Kotlin Generics example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Kotlin Foundations for Android exercise changes the conditions. In Android Development lesson 28 — Use Kotlin Generics, use that observation as the checkpoint for this exact Kotlin Foundations for Android topic rather than generalizing it beyond the evidence.

The idea behind Kotlin Generics

Before adding more syntax, make the state of the system observable. That habit matters especially when working with Kotlin Generics. At the beginner stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. For Kotlin Generics, apply this check in the context of the Kotlin Foundations for Android workflow before carrying the assumption into later Android Development work.

There are usually several ways to accomplish the same visible result. The important skill is knowing which guarantees differ when you choose one form of Kotlin Generics over another. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. The specific test here is about Kotlin Generics: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above. In Android Development lesson 28 — Use Kotlin Generics, use that observation as the checkpoint for this exact Kotlin Foundations for Android topic rather than generalizing it beyond the evidence.

Questions to answer about Kotlin Generics

1. What is the smallest input or state that makes Kotlin Generics observable?
2. What does success look like, and how can you prove it without relying on a vague UI message?
3. Which configuration, permissions, types, versions or environment details can change the result?
4. Which failure is most likely for a beginner, and what evidence distinguishes it from a different failure?
5. What should remain true after the example is repeated, automated or moved to another environment?

Mental model before syntax

In the Kotlin Foundations for Android part of this learning path, Kotlin Generics is deliberately introduced now because later lessons depend on the boundary it establishes. At the beginner stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. In this lesson's Kotlin Generics example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Kotlin Foundations for Android exercise changes the conditions. In Android Development lesson 28 — Use Kotlin Generics, use that observation as the checkpoint for this exact Kotlin Foundations for Android topic rather than generalizing it beyond the evidence.

A production system rarely fails at the exact line shown in a beginner example, so this section connects Kotlin Generics to the surrounding runtime and operational context. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. The specific test here is about Kotlin Generics: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above. In Android Development lesson 28 — Use Kotlin Generics, use that observation as the checkpoint for this exact Kotlin Foundations for Android topic rather than generalizing it beyond the evidence.

Terminology and boundaries

For a Android developer, Kotlin Generics becomes useful when it changes a decision you can verify. At the beginner stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. The specific test here is about Kotlin Generics: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above. In Android Development lesson 28 — Use Kotlin Generics, use that observation as the checkpoint for this exact Kotlin Foundations for Android topic rather than generalizing it beyond the evidence.

The practical question behind use kotlin generics is not simply whether the feature exists, but what behavior it gives you control over. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. The specific test here is about Kotlin Generics: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above. In Android Development lesson 28 — Use Kotlin Generics, use that observation as the checkpoint for this exact Kotlin Foundations for Android topic rather than generalizing it beyond the evidence.

Evidence table

What you inspect	What it tells you	What it does not prove
Source/configuration for Kotlin Generics	What you asked the platform/runtime to do	That the request actually succeeded
Build/validation output	Whether static checks accepted the artifact	That production data and permissions behave correctly
Runtime/result output	What happened for this input	That every edge case is safe
Logs/diagnostics	Where the system spent time or failed	The root cause without interpretation
Repeat test	Whether behavior is reproducible	That the design is optimal

How the mechanism behaves step by step

Before adding more syntax, make the state of the system observable. That habit matters especially when working with Kotlin Generics. At the beginner stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. Keep this point tied to Kotlin Generics. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Kotlin Foundations for Android lesson are specific to this mechanism. In Android Development lesson 28 — Use Kotlin Generics, use that observation as the checkpoint for this exact Kotlin Foundations for Android topic rather than generalizing it beyond the evidence.

For this part of Use Kotlin Generics, move beyond the earlier mental model and ask how the behavior survives repetition. Run or reproduce the step twice, change the ordering or boundary case where safe, and verify that the same invariant still holds. A reliable Kotlin Foundations for Android workflow is one that produces evidence you can compare, not one that succeeds only when the exact tutorial sequence is copied.

Syntax or configuration anatomy

In the Kotlin Foundations for Android part of this learning path, Kotlin Generics is deliberately introduced now because later lessons depend on the boundary it establishes. At the beginner stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. For Kotlin Generics, apply this check in the context of the Kotlin Foundations for Android workflow before carrying the assumption into later Android Development work.

A production system rarely fails at the exact line shown in a beginner example, so this section connects Kotlin Generics to the surrounding runtime and operational context. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. In this lesson's Kotlin Generics example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Kotlin Foundations for Android exercise changes the conditions. In Android Development lesson 28 — Use Kotlin Generics, use that observation as the checkpoint for this exact Kotlin Foundations for Android topic rather than generalizing it beyond the evidence.

Worked example: Kotlin Generics

The following kotlin example is written specifically for this lesson. Read the requirement first, then predict the important result before running or reproducing it.

data class InventoryItem(val sku: String, val quantity: Int)

fun lowStock(items: List<InventoryItem>): List<InventoryItem> =
    items.filter { it.quantity < 5 }.sortedBy { it.quantity }

fun main() {
    val items = listOf(InventoryItem("KB-100", 8), InventoryItem("MS-200", 3))
    println(lowStock(items))
}

Expected observation

Only MS-200 is returned as low stock.

Read the example deliberately

• Line/construct 1: data class InventoryItem(val sku: String, val quantity: Int) — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 2: fun lowStock(items: List<InventoryItem>): List<InventoryItem> = — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 3: items.filter { it.quantity < 5 }.sortedBy { it.quantity } — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 4: fun main() { — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 5: val items = listOf(InventoryItem("KB-100", 8), InventoryItem("MS-200", 3)) — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 6: println(lowStock(items)) — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 7: } — identify what state or contract this introduces, then trace where that state is consumed.

Do not stop at “it ran.” Change one meaningful value related to Kotlin Generics, predict the new result, run/reproduce the example again, and explain why the output changed. That mutation test is a stronger check of understanding than copying the original result.

Worked example built from a real requirement

For a Android developer, Kotlin Generics becomes useful when it changes a decision you can verify. At the beginner stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. For Kotlin Generics, apply this check in the context of the Kotlin Foundations for Android workflow before carrying the assumption into later Android Development work.

In Worked example built from a real requirement, look at Kotlin Generics through the constraint that matters in this part of the lesson: make the relevant state visible before you change it, then compare the observed result with the contract you expected. In Android Development, this prevents a local-looking edit from hiding an environment, data, permission, lifecycle or runtime assumption. Record the evidence from this step because the next decision in the Kotlin Foundations for Android module should be based on what you measured rather than on a repeated rule of thumb.

Trace the example line by line

Now apply Kotlin Generics to the current Trace the example line by line concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Android Development runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

There are usually several ways to accomplish the same visible result. The important skill is knowing which guarantees differ when you choose one form of Kotlin Generics over another. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. For Kotlin Generics, apply this check in the context of the Kotlin Foundations for Android workflow before carrying the assumption into later Android Development work. In Android Development lesson 28 — Use Kotlin Generics, use that observation as the checkpoint for this exact Kotlin Foundations for Android topic rather than generalizing it beyond the evidence.

Failure-mode matrix

Symptom	Likely category	First evidence to collect
The Kotlin Generics behavior never occurs	configuration / control flow	verify the relevant code/configuration is actually reached
Build or validation fails	syntax / type / unsupported option	read the first meaningful diagnostic, not the last cascade message
Works locally but not elsewhere	environment / version / permission	compare runtime versions, identity, configuration and data
Result is valid but wrong	assumption / data shape / business rule	inspect intermediate values and boundary conditions
Intermittent behavior	concurrency / timing / external dependency	add timestamps, correlation IDs or deterministic reproduction

Variants you will meet in real code

In Variants you will meet in real code, look at Kotlin Generics through the constraint that matters in this part of the lesson: make the relevant state visible before you change it, then compare the observed result with the contract you expected. In Android Development, this prevents a local-looking edit from hiding an environment, data, permission, lifecycle or runtime assumption. Record the evidence from this step because the next decision in the Kotlin Foundations for Android module should be based on what you measured rather than on a repeated rule of thumb.

For the Variants you will meet in real code part of Use Kotlin Generics, use a separate verification pass rather than repeating the earlier explanation. Focus on Kotlin Generics under one changed condition and write down the before/after evidence. This is verification pass 2 for Android Development lesson 28: the useful outcome is a concrete observation—output, state, diagnostic, generated artifact, query result or test result—that another learner can reproduce in the Kotlin Foundations for Android workflow.

Interactions with neighboring concepts

This section needs a different question from the earlier explanation: what would make Kotlin Generics fail specifically while working through Interactions with neighboring concepts? Choose one realistic boundary, reproduce it deliberately, and inspect the first useful diagnostic or intermediate value. The aim in Use Kotlin Generics is to recognize the mechanism under changed conditions, not to repeat the same successful path with different wording.

Now apply Kotlin Generics to the current Interactions with neighboring concepts concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Android Development runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

Failure modes that reveal misunderstanding

Before adding more syntax, make the state of the system observable. That habit matters especially when working with Kotlin Generics. At the beginner stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. In this lesson's Kotlin Generics example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Kotlin Foundations for Android exercise changes the conditions.

Now apply Kotlin Generics to the current Failure modes that reveal misunderstanding concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Android Development runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

Choosing between common alternatives

In the Kotlin Foundations for Android part of this learning path, Kotlin Generics is deliberately introduced now because later lessons depend on the boundary it establishes. At the beginner stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. The specific test here is about Kotlin Generics: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

This section needs a different question from the earlier explanation: what would make Kotlin Generics fail specifically while working through Choosing between common alternatives? Choose one realistic boundary, reproduce it deliberately, and inspect the first useful diagnostic or intermediate value. The aim in Use Kotlin Generics is to recognize the mechanism under changed conditions, not to repeat the same successful path with different wording.

Testing the behavior

For a Android developer, Kotlin Generics becomes useful when it changes a decision you can verify. At the beginner stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. Keep this point tied to Kotlin Generics. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Kotlin Foundations for Android lesson are specific to this mechanism.

The practical question behind use kotlin generics is not simply whether the feature exists, but what behavior it gives you control over. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. Keep this point tied to Kotlin Generics. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Kotlin Foundations for Android lesson are specific to this mechanism.

Maintainability and readability

Before adding more syntax, make the state of the system observable. That habit matters especially when working with Kotlin Generics. At the beginner stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. The specific test here is about Kotlin Generics: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

This section needs a different question from the earlier explanation: what would make Kotlin Generics fail specifically while working through Maintainability and readability? Choose one realistic boundary, reproduce it deliberately, and inspect the first useful diagnostic or intermediate value. The aim in Use Kotlin Generics is to recognize the mechanism under changed conditions, not to repeat the same successful path with different wording.

Performance or operational implications

In the Kotlin Foundations for Android part of this learning path, Kotlin Generics is deliberately introduced now because later lessons depend on the boundary it establishes. At the beginner stage, the goal is not to cover every advanced option. It is to establish the correct mental model and the verification habit that later pages can extend. Where the platform has version-specific behavior, prefer the current official documentation and check the version shown by your own tools before assuming an older screenshot or blog post is authoritative. Keep this point tied to Kotlin Generics. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Kotlin Foundations for Android lesson are specific to this mechanism.

A production system rarely fails at the exact line shown in a beginner example, so this section connects Kotlin Generics to the surrounding runtime and operational context. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. For Kotlin Generics, apply this check in the context of the Kotlin Foundations for Android workflow before carrying the assumption into later Android Development work.

Practice variation

This section needs a different question from the earlier explanation: what would make Kotlin Generics fail specifically while working through Practice variation? Choose one realistic boundary, reproduce it deliberately, and inspect the first useful diagnostic or intermediate value. The aim in Use Kotlin Generics is to recognize the mechanism under changed conditions, not to repeat the same successful path with different wording.

Now apply Kotlin Generics to the current Practice variation concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Android Development runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

Review questions

Now apply Kotlin Generics to the current Review questions concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Android Development runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

There are usually several ways to accomplish the same visible result. The important skill is knowing which guarantees differ when you choose one form of Kotlin Generics over another. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. In this lesson's Kotlin Generics example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Kotlin Foundations for Android exercise changes the conditions.

A production-oriented walkthrough for Kotlin Generics

1. Establish the Kotlin Generics behavior

2. Inspect the Kotlin Generics behavior

3. Implement the Kotlin Generics behavior

A useful variation is to introduce one boundary case that is plausible for Kotlin Generics: an empty value, a missing permission, an unexpected type, a repeated operation, an unavailable dependency, or a larger-than-normal input. The exact case depends on the technology, but the reasoning is the same—state the invariant you expect to remain true, then verify it explicitly. In this lesson's Kotlin Generics example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Kotlin Foundations for Android exercise changes the conditions. In Android Development lesson 28 — Use Kotlin Generics, use that observation as the checkpoint for this exact Kotlin Foundations for Android topic rather than generalizing it beyond the evidence.

4. Exercise the Kotlin Generics behavior

5. Challenge the Kotlin Generics behavior

Now apply Kotlin Generics to the current A production-oriented walkthrough for Kotlin Generics concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Android Development runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

6. Verify the Kotlin Generics behavior

7. Harden the Kotlin Generics behavior

Harden this step in the context of build a small Compose-based application with navigation, state, persistence and networking. Keep the change small enough that you can state the expected result before executing it. Capture the relevant input, configuration or code, then record the observable result. If the result differs from the prediction, do not add more changes yet; narrow the mismatch using diagnostics appropriate to Android Studio, Android SDK and emulator. The specific test here is about Kotlin Generics: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

This section needs a different question from the earlier explanation: what would make Kotlin Generics fail specifically while working through A production-oriented walkthrough for Kotlin Generics? Choose one realistic boundary, reproduce it deliberately, and inspect the first useful diagnostic or intermediate value. The aim in Use Kotlin Generics is to recognize the mechanism under changed conditions, not to repeat the same successful path with different wording.

8. Document the Kotlin Generics behavior

Where Kotlin Generics implementations commonly go wrong

Treating Kotlin Generics as syntax instead of behavior

If you can reproduce the syntax but cannot predict the state after it runs, the lesson is not finished. Rewrite the example in your own words and name the input, operation and observable result.

Copying a configuration from a different version

Android Development tooling evolves. Compare the documentation version, runtime/tool version and project settings before assuming that a screenshot or command from another environment applies unchanged.

Verifying only the happy path

A successful first run proves one path. Add at least one negative or boundary case relevant to Kotlin Generics. The failure should be intentional and the diagnostic should make sense.

Hiding the important state behind too much abstraction

Abstraction is useful after the behavior is understood. During the first implementation of Kotlin Generics, keep the decisive state and control flow visible enough to debug.

Troubleshooting from evidence, not guesses

Use this order when Kotlin Generics does not behave as expected:

1. Reproduce the smallest failing case.
2. Confirm the actual version/toolchain/environment.
3. Capture the first meaningful diagnostic or unexpected value.
4. Verify identity, permissions and configuration if the operation crosses a service boundary.
5. Inspect intermediate state rather than only the final UI.
6. Change one variable and rerun.
7. Compare the corrected behavior with a negative case.
8. Record the final cause so the same failure is faster to diagnose next time.

Challenge the worked example

Extend the worked scenario so that Kotlin Generics must handle one additional real constraint. Choose one: a second data shape, a failed dependency, an invalid input, a permission difference, a repeat operation, or a larger workload. Before implementing the change, write down the behavior you expect and the evidence that will prove it.

Your result is complete when another learner can reproduce the change from your notes, observe the expected behavior, and intentionally trigger at least one documented failure without damaging their environment. The specific test here is about Kotlin Generics: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

Evidence that you understand Kotlin Generics

• Can you define Kotlin Generics without using the exact wording of an API/reference page?
• Can you identify the boundary where Kotlin Generics begins and where another concept takes over?
• Can you predict the result of the worked example before running it?
• Can you explain one failure from evidence rather than guessing?
• Can you name one production constraint that the beginner example intentionally simplifies?
• Can you repeat the example from a clean state?

What should stay with you

• Kotlin Generics is useful because it controls observable behavior, not because it adds another piece of syntax to memorize.
• Verification belongs in the workflow: build/check, run/reproduce, inspect, challenge, and repeat.
• The Kotlin Foundations for Android module uses this lesson as a foundation for the next decisions in the Android Development learning path.
• Official documentation is the source of truth for version-specific contracts; tutorials should teach you how to read and apply those contracts.

Documentation to keep beside this lesson

The following primary documentation was used as a factual reference map for this lesson. ScrutnLearn's explanation is original synthesis rather than copied documentation prose.

• Kotlin coroutines guide
• Kotlin documentation
• Android Basics with Compose
• Android Developers
• Android app architecture