ilkeraslan / dota2compose

An Android app to show dota2 related info using JetpackCompose.

dota2compose

An app to show dota2 related information using JetpackCompose.

heroes teams

API

The data is provided by both OpenDota API and Steam API. In order to start development, you need to get a Steam API Key, and define an environment variable with the name "STEAM_API_KEY".

Stack

• JetpackCompose
• Coil
• Coroutines
• Flow
• Hilt
• OkHttp
• Retrofit
• kotlinx.serialization
• RxKotlin

Contributing

Anyone wants to practice JetpackCompose skills may feel free to contribute to the project.

If you want to work on an issue, please ask first so that I can assign it to you. If you have an idea for improvement just create an issue in order to discuss together.

Download

dota2compose's Issues

Add logo

Create Splash Screen

We should create a Splash Screen using the new Splash Screen API.

The Screen should have:

• The official DOTA2 logo
• App title (dota2compose)
• Background color: choose whatever works the best 😀

Useful documentation: https://developer.android.com/guide/topics/ui/splash-screen

Bump Coil to 2.2.2

Show Players for Teams

Add PlayersScreen

We should have a Players Screen which is capable of showing professional Dota2 players.

In this task:

• This Screen should be integrated into Bottom Navigation like HeroesScreen and TeamsScreen.
• The Screen should show the players by their rank in descending order.

The Screen should be built using Jetpack Compose.

This issue is blocked by #4, so you can mock a list of 20 players in a separate file and show that. When #4 is resolved, another issue will be created to integrate the real repository.

Create playersByRank method

We should create a playersByRank() method inside the PlayersRepository which will get players by their rank.

This repository should:

• Have a method named playersByRank() which makes an API call to this endpoint.
• This method should return a list of account id's of the players.

Fix colors

Sort teams by wins

Bump Compose Compiler to 1.3.2

Add HeroDetails Screen

We should have a HeroDetails Screen which is capable of showing a Hero's details.

Specifically this screen should have:

• Hero's image
• Hero's name and type
• Some of the main stats of a Hero (like baseHealth, moveSpeed, baseMana etc.)

The Screen should be built using Jetpack Compose.

Create playerByID method

We should create a playerByID method inside the PlayersRepository which will have a method to get a player by its id.

This repository should:

• Have a method named playerByID() which makes an API call to this endpoint.
• This method should return a a player if it has been found, otherwise null.

Docs: https://docs.opendota.com/#tag/players%2Fpaths%2F~1players~1%7Baccount_id%7D%2Fget

Migrate to TOML for versions

Create HeroRankings Calll

Value

In order to show the user the best players of a given hero, we should create an API call.

User Stories

• I can call the HeroesAPI.getBestPlayers(heroID: Long) in order to get the player rankings for the given hero.

Endpoint

https://docs.opendota.com/#tag/rankings

Add TeamDetails Screen

We should have a TeamDetails Screen which is capable of showing a Team's details.

Specifically this screen should have:

• Team's name and stats

The Screen should be built using Jetpack Compose.

Introduce LeaugesRepository

Scope

We would like to show the available dota2 leagues information on a dedicates screen, thus we need a repository to fetch the data.

User Stories

As a user, I can:

• Get a list of Leagues.
• Get a given League.
• Get the matches of a League.
• Get the teams of a League.

Endpoints

The repository will return null for each method for now.

Introduce LeaguesAPI

Scope

We would like to show the available dota2 leagues information on a dedicates screen, thus we need a repository to fetch the data.

User Stories

As a user, I can:

• Get a list of Leagues.
• Get a given League.
• Get the matches of a League.
• Get the teams of a League.

Endpoints

https://docs.opendota.com/#tag/leagues

Bump Kotlin to 1.7.0

Upgrade TargetSDK to 33

README.md file has incorrect reference

in readme.md file heroes points to teams and teams points heroes.
it would be good to fix them.

Add T&C and Privacy Policy

Introduce feature packaging

We should organize the packaging by feature, not by layer. For instance, Teams related components go into teams package.

Exclude idea and build files