Project Material
One thing I don't understand, Google uses multiple types of their own design in their apps, you can't even understand which one is which. I'm confused what to use 😕
sometimes it follows their guidelines, sometimes it's not
Project Material
sometimes it follows their guidelines, sometimes it's not
like what's this inconsistency
Like okay I'd understand these:
Background: colorSurfaceContainer
Cards: colorSurface
but what to use in top App bar and BottomNav? especially for collapsible Toolbar
Background: colorSurfaceContainer
Cards: colorSurface
but what to use in top App bar and BottomNav? especially for collapsible Toolbar
Forwarded from GApps Leaks (Shiv (AssembleDebug))
Google has widely started rolling out the new file uploading UI in Google Drive app.
I spotted this UI change back in August 2024. The new UI makes it easier to track files you are uploading and what you have already uploaded.
@GappsLeaks
I spotted this UI change back in August 2024. The new UI makes it easier to track files you are uploading and what you have already uploaded.
@GappsLeaks
👍2
if any of these yahoo, openai or perplexy buys chrome, we're all cooked
😁6
Project Material
?
keeping it like that?
Anonymous Poll
59%
yay
21%
nay
21%
I'll show my own design in the comments (kys if you don't)
Project Material
?
i bet warning dialog is better than opening storage access page right after opening the app
👍2
Project Material
it uses primary container color now, instead of secondary container
I may use Material3Expressive, but it's uncooked
GApps Leaks
Day 2 of sharing expressive shit. Google Drive app. @GappsLeaks
Should i use lamexpressive theming?
Anonymous Poll
49%
Yes (Lame)
35%
No (Sigma)
16%
Yesn't (Use an expressive theme with fixed dimensions from the non-Expressive Material3 theming)
Project Material
Should i use lamexpressive theming?
Note that most of the dimensions in the current "theming" are basically ruining the whole Material You perfection.
I should like to mention that, in order to publish functional builds, I am presently obliged to disregard numerous scenarios—beginning with the Predictive Back configuration. On Android 14, it is quite literally half-implemented and further induces a theming anomaly.
As for the database, favouriting a video currently utilises SharedPreferences rather than Room, as I have yet to grasp the intricacies of Room. If anyone is well-versed in its use, you are most welcome to amend the source code, which I have linked a few messages above on GitHub.
I have endeavoured to accommodate a broad range of scenarios, from multi-item selection to search functionality and even the exclusion of specific source paths.
Future suggestions are warmly invited—though I kindly ask that you refrain from commenting on the media player for now. I shall integrate it once I have devised an optimal implementation suited to the application.
(le brit)
I have endeavoured to accommodate a broad range of scenarios, from multi-item selection to search functionality and even the exclusion of specific source paths.
Future suggestions are warmly invited—though I kindly ask that you refrain from commenting on the media player for now. I shall integrate it once I have devised an optimal implementation suited to the application.
(le brit)
👍1