Комментарии:
Alot of efforts for basic stuff and like someone else said it's scary to use for complex designs and not good for back and forth between figma and android studio
Ответитьui-packages doesn't appear after clicking on 'Finish
Ответитьwhen i attempt to import my code over to android studio i am met with an SVG error, does anyone know how to solve this issue
ОтветитьDanke dir - very helpful!
ОтветитьGenius!
Ответитьit's showing me ' Not a JSON Object: null ' in gradle build
ОтветитьI'm getting negative feels about the generated code. Same thing with the constraint layout generated code. I always manually modified it.
ОтветитьDo you have an available promo code for your Android course?
ОтветитьWhich android studio theme are you use?
ОтветитьThis didn't work for my team. Our designs are somewhat complex, though if you have something as simple as two labels side-by-side and need text to be custimizable, Relay messes this up because Figma doesn't have a notion of widgets being constrained to edges of other widgets, so what happens here is Relay generates a Composable with two Labels in a coordinate system. This means when the left-most text is longer than it was in the Figma design, it will overlap the label adjacent to it. At the moment, it's much easier for us to just port the design manually.
ОтветитьThanks
ОтветитьAndroid studio should also include some sort of drag drop into compose, similar to xml. It really speed things up and is easier to visualize design.
Ответитьplease make video how to create widget using jetpack glance
ОтветитьVERY COOL 👍👍👍👍
Thank you BRO
Designers will not do these manipulations for us, and devs usually does not have write acces to figma design. Will look forward for updates.
Ответить@PhillipLackner - what about a bottom navigation bar with animated icons?
ОтветитьRelay is friggin' magic... very cool and I hope for success. I too have reservations for now -- Relay is in alpha and is autogenerating code for relatively new Compose (which itself is just now settling down to stability), so that seems like a very brittle combination!
Using Figma+Relay for isolated UI components like a button makes sense, but the more complicated nested layouts like an entire Screen seem scary - the odds increase that you will need to perform some simple change or optimization to the Compose hierarchy (adding 'remember', state hoisting, etc.). That might be a quick and easy Kotlin change, but you should not edit the generated code. It could be difficult or impossible to change this back in Figma.
Great video. Thanks!
Ответитьthat's why we use jetpack compose
Ответитьrevoluation
ОтветитьHey philip can u teach us figma in next vids
ОтветитьHi Phillip thanks for reading our mind. By the way is there any plugin to convert it into XML too.
ОтветитьKinda cool for someone that just starts with compose
ОтветитьBtw what's is your theme name ? I really love it but kind find it
ОтветитьThanks for sharing :)
ОтветитьAdobe will say soon how it's cool🤣
ОтветитьGreat video. Philip
ОтветитьThe idea is nice... But the reality it's better to build a component by our own. The generated code it's not so good
ОтветитьWow
ОтветитьNice. From android dev summit you can summarize dev updates in your style.
ОтветитьJust liking the vid. 🫡
Ответитьwaiting for this so longggg
ОтветитьPlease need a video about Android Interview roadmap for experienced.
ОтветитьFirst comment: From Nepal guru
Ответить