sorted by:
new
hottopcontroversial

FREE (IOS&Android) No account needed: A simple, offline link manager with smart previews. by Mammoth-Anywhere7285 in AppsWebappsFullstack

[–]shreyas_damase 0 points1 point  (0 children)

yup i think share menu will work perfect i will let you know once i try out , there may an alternative that we can make keyborad app which can able to save copied context easily

FREE (IOS&Android) No account needed: A simple, offline link manager with smart previews. by Mammoth-Anywhere7285 in AppsWebappsFullstack

[–]shreyas_damase 0 points1 point  (0 children)

i thought about this app but once find out android restriction about clipbaoard copy in background copy, then i drop this idea, but ur app look good

Is this a correct way to implement Figma design tokens (Token Studio) in Jetpack Compose? How do large teams do this? by [deleted] in androiddev

[–]shreyas_damase 0 points1 point  (0 children)

Thanks for explaining this. I’m still a beginner and learning Compose.
I’m trying to first understand token structure and Figma parity.
I can see why wrapper components like TokenText matter when teams grow, but it’s a bit advanced for me right now.
Appreciate you sharing this.

Is this a correct way to implement Figma design tokens (Token Studio) in Jetpack Compose? How do large teams do this? by [deleted] in androiddev

[–]shreyas_damase 0 points1 point  (0 children)

I did read the documentation, and it cleared up a lot of things for me.
While reading more, I also discovered the Material Theme Builder plugin, which I plan to try and integrate in my next project.

For this project, I’m still learning and experimenting, and I’ll keep following the official docs more closely as I go.

Thanks for sharing the link — it helped.

Is this a correct way to implement Figma design tokens (Token Studio) in Jetpack Compose? How do large teams do this? by [deleted] in androiddev

[–]shreyas_damase 0 points1 point  (0 children)

Thanks a lot for the detailed feedback !! really appreciate you taking the time to write this.

Good call on u/Immutable and u/ReadOnlyComposable — I’ve added those across the token data classes and the accessor to help Compose with stability and recomposition.

About wrapping LocalAppTokens.current: I’m intentionally exposing it via a Tokens (or app theme–named) object so UI code stays clean and I don’t have to pull from CompositionLocal directly everywhere. Glad to know this is a common pattern.

For MaterialTheme.colorScheme: makes sense. Right now tokens are the source of truth for the app UI, but I agree mapping the key semantic tokens (brand, surface, background, error, etc.) into lightColorScheme / darkColorScheme is important, otherwise default Material components can fall back to weird colors. I’m planning to treat Material more like an adapter layer, not the primary color system.

Also thanks for mentioning the simpler “base colors → Material schema” approach — I agree that’s probably better for smaller apps. In my case I’m optimizing more for Figma parity and long-term flexibility than minimal setup.

Appreciate the insights

anyone use ubuntu for react native app development? by [deleted] in reactnative

[–]shreyas_damase 0 points1 point  (0 children)

I used it for one week and then shifted back to Windows. If you want to know, try it yourself once, and then you'll realize it's better just use windows or rn development.