Keyur

Checkout DayTask! 🚀 My new Android task manager built with Jetpack Compose (Kotlin). It features real-time progress tracking, and a sleek dark UI and some other features that are mentioned in link. Organize your life and projects easily! 👉 Link: github.com/Keyur1291/DayT…

@rynxvyrn09 Device?

Coloros 16.1

@android_poet Currently working on a similar feature(Signing documents) used transformable +graphics layer to do the job XD. Also took a lot of inspiration from Philip lackner for the scale in/out logic.

@Keyur12901 developer.android.com/develop/ui/com…

All the Jetpack Compose warriors, does anyone want to build this?

@android_poet Crazy how i managed to reduce the apk size tp 100mb from 127 just by removing pngs that the old employee thought was a good idea to use lmao, guy used pngs for everything even a small dot icon bruh...😭

I always hate seeing large app sizes on iOS and Android. Sometimes I feel there’s some one-line optimization they’re not telling us how to enable.

@SwiggyCares @Swiggy It was Peri-Peri fries

@Keyur12901 @Swiggy @Keyur12901 Appreciate your patience. Could you kindly let us know the item names that are missing from your order? ^Maddie

@Swiggy @SwiggyCares I ordered food from McDonald's and had items missing in my order, when i tried to report it the app doesn't even let me select the missing item. OrderId: #226171440290061

@JorgeCastilloPr New theme support was added which kinda looks good and bad at the same time lol

Did you try the Panda already? 🐼 Thoughts?

@dlcEarth @Cartidise It is Fami, the one who drew this wrote her name in the caption

@Keyur12901 @Cartidise I read csm too, that's not fami bro that's someone else but I don't remember her at all

OPPO really nailed it with the Find X9 Pro ABSOLUTELY CANNOT WAIT FOR THE X9 ULTRA

@Cartidise Dodged a bullet by choosing this over sammy haha...

@Keyur12901 Great choice

@dlcEarth @Cartidise Fami from chainsaw man

@Keyur12901 @Cartidise W pic, also who's that ins your pfp? I don't recognise her at all.

@PiListingNews 33

Pick a lucky number from 1 – 52. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 5 numbers hide a surprise of $2500 5 Winners will be picked randomly in 72 hours

@android_poet The fact that i can practically see my whole keyboard printed on it's screen every time i open my Air is so bizarre lmao

Random first-year Indian students think MacBook pictures are banger content 😭😭 (broken MacBook for algo boost)

@SLKVinyl Good old zero two...

Drop your Android Home Screen and I’ll rate it out of 10 👀

@AssembleDebug Yet no signs of qpr release for aosp

Good news for Pixel Watch 2 and Pixel Watch 3 WearOS 6 based on Android 16 starts rolling out today. Factory images has been made available for these watches along with Pixel Watch 4.

@_anpurnama @android_poet Depends on the complexity of the data that is being sent from API. In my use case when i was working with poke API i wrote 2 separate VMs for the list and the details pages(passed Pokemo's id with saved state handler to VM directly) because the details page had complex structure.

@android_poet @Keyur12901 would you elaborate more on separate viewmodel creation? for example, the screen structure are image carousel and details section. each came from different endpoint, each warrant separate viewmodel?

• Keep the UI layer pure and side-effect-free. • Use a ViewModel (or separate state holders) to manage all UI state. • Perform expensive operations in the Repository layer away from the UI. • The UI should not care whether data comes from network, local DB, or a sync process. • Handle navigation in the ViewModel, using a clean abstraction create a Navigator.

@android_poet Yeah I'm trying to do that in my current project, i even checked out Philip lackner's video/repo on using enum classes to show exceptions based on its' code.

@Keyur12901 Yes, create a proper error parser for the entire API system along with error codes, and handle errors accordingly! Sometimes, many errors can just be shown as a snackbar message, but in some cases like when you get an error code such as 422 you need a proper parser.

@android_poet Yeah that's reasonable. My senior said the same thing, he even mentioned adding response handlers and their classifications to manage different network exceptions and tailor it to show different messages in simpler language.

Yes, that’s a double-edged sword but handling nulls or empty states can become a nightmare. From my recent experience, it’s best to divide APIs as much as possible. If only three APIs are related to each other, avoid making additional network calls. Instead, create a separate ViewModel for them. This approach will make the system more scalable in the future.

@android_poet Oh i assumed you use separate flow for loading based on the snippets lol, my bad But I'd understand that as well since wrapping the ui state introduces a lot of boiler plate code while writing ui(compared to separate loading flow at least)

@Keyur12901 It’s the same I haven’t included it in the file because it would become very large, but if you read the code, there’s an AppUI.State.