An additional challenge we’d like to see Mid-Level and Senior delivering is to implement persistent storage of messages in a database, and an architecture allowing UI classes to observe data form the database so that it always displays the latest information.

The user should be able to filter characters by season appearance

• Filter work for List and Search

Inside Common module create a Common class that instance the retrofit client.

Ideally give to option to instantiate it with different urls

If a previous message was sent more than an hour ago, or there is no previous messages, it should be sectioned as in Screenshot 2. The format for this is “{day} {timestamp}”.

• Order newest items in the bottom
• Add message and Send button = add to chat list
• Send Messages on Right, received on Left
• Use Bubble design

https://codelabs.developers.google.com/codelabs/android-paging/index.html?index=..%2F..%2Findex#0

One Single Activity app

The text entered into the Text Entry Box should animate into the Message List akin to Apple’s Messages app shown in Screenshot 3. This video makes this clearer: https://youtu.be/WkYdn5Yt1Dg

https://github.com/jmfayard/refreshVersions

https://github.com/ChuckerTeam/chucker

ViewBinding

The user should be able to search for a character by name.

• Search responsible while user is typing

Make home screen with a list of feature in the app for easy navigation

List of Breaking Bad characters

Data:

• Image
• Character name

Future Functionality
The user selects a character to transition to Char Details #10

Add git hook to ktLint format before push

Data:

• Image
• Name
• Occupation
• Status
• Nickname
• Season appearance

A message has a tail when any of the following 3 criteria are met:

• It is the most recent message in the conversation
• The message after it is sent by the other user
• The message after it was sent more than 20 seconds afterwards

“Migrating SharedPreferences to Jetpack DataStore” by Juraj Kušnier https://link.medium.com/DntLRiVN89

Make some automated answer without AIP call

Hello,

We've tried to activate or update your repository on Depfu and couldn't find any supported dependency files. If we were to guess, we would say that this is not actually a project Depfu supports and has probably been activated by error.

Monorepos

Please note that Depfu currently only searches for your dependency files in the root folder. We do support monorepos and non-root files, but don't auto-detect them. If that's the case with this repo, please send us a quick email with the folder you want Depfu to work on and we'll set it up right away!

How to deactivate the project

• Go to the Settings page of either your own account or the organization you've used
• Go to "Installed Integrations"
• Click the "Configure" button on the Depfu integration
• Remove this repo (Canato/showcase) from the list of accessible repos.

Please note that using the "All Repositories" setting doesn't make a lot of sense with Depfu.

If you think that this is a mistake

Please let us know by sending an email to [email protected].

This is an automated issue by Depfu. You're getting it because someone configured Depfu to automatically update dependencies on this project.

The API endpoint can be accessed at API LINK

{
    'profiles': [{
	'username': string,
	'weeklyXP': number,
	'isCurrentUser': boolean,	
    }]
}

interface LeaderboardResponse {
    profiles: Profile[];
}

interface Profile {
    username: string;
    weeklyXP: number;
    isCurrentUser: boolean;
}

All fields are required and can be assumed to be present

1. As a user, you can see the header of the Leaderboard, which displays a header and a flag to indicate the time remaining before the leaderboard resets (for this purpose, this can be a string rather than a timer)
2. As a user, you're able to see the usernames of everyone in the leaderboard, along with their position and the amount of XP they've earnt this week. The users are sorted from top to bottom, by XP earnt this week
3. As a user, my own profile is highlighted with a slightly grey background, as in the design

Data Source should be inside :data_source module.

Cache information;
DTO class;

• method get all, return list dto

• method get by id, return dto

• API endpoint: https://breakingbadapi.com/api/characters

• README
• CODEOWNER
• CHANGELOG
• Github branch/project settings
• CI Workflow
• Gradle Properties, Lib Versions [use kotlin]
• Add ktLint
• Add hooks #4

• Run refresh version gradle command
• If changes Open PR