Heya David - Thanks for your comments!

1. Most of the lag with using Abstract comes from not using professional level hardware and attempting to run it on consumer-level laptops. ( they're also improving their software speeds with new updates. It's already much faster than 8-months ago ) Have you tried running it on a trashcan?

2. For all the templates, libraries, components and other deets that keep things runnig smoothly-consistently I worked with the Lyft Design org to set up a Lyft Product Language team and LPL Documentation. Once we switched over to Figma I also helped design an IC linter app which works in tandem with Lyft's IDE linters. Having someone on the team focusted on standardization really helps!

3. Yes, I recommend switching to a systems-representation of your application within Abstract. This will not only make things easy to find for everyone but will also allow things to be found which exist across many different areas of the app. Two things to recommend here: A. You can still have feature files and add index files that just have a bunch of links to different feature files containing sub-systems of something like the 'referrals system'. B. You can actually cross-link files organized systemically to make them easy to navigate. While not as easy as Figma, you can make a global linking symbol that contains an editable title and copyable link section to other areas within your Abstract environment.

#staysafe