Looking for feedback on whether capturing & de...
# compose
z
Looking for feedback on whether capturing & decorating screenshots in compose is a good idea or not. More details in 🧵
Capturing screenshots of composables on desktop is a breeze nowadays. There are still a lot of them though, across configurations, locales, screen sizes, etc, Im up to almost 1000 for one of my apps. Most of them are only used for quality control, but a subset of say 20 are used in the play store and other promotional content. Usually Ill edit them "outside of compose" .. add some device frame, some background, additional text, etc. All of which could be done in compose, so why not? Im writing this to check if anyone else has gone down this rabbit hole? Pros/cons? My personal take is that if everything remains in compose, you can have a single source of truth for all the colors, fonts, etc. Youre practically decorating the screenshots with components from the same design system. One caveat I can think of is that this might not be as creative/expressive, for example - one pattern Ive seen a lot is "zooming in" on portions of the screenshot, making some elements larger, etc. This is still possible with compose, but at that point it might just be easier to do it "manually". So, has anyone else thought about doing this? It seems like a pretty huge win to be able to generate all those screenshots, with all that jazz, automatically, and have it hooked up to CI so that say, play store and app store screenshots are just automatically updated - across soooo many languages.
a
I have been thinking about this a lot too. I just didn't get time to come around it
👀 1