You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regarding of the strategy to release the new version with the styles2variables migration
I think the best approach is to keep the current libraries instead of creating a duplicate of mobile and desktop libraries.
Pro:
Avoid double maintenance
Avoid duplication of published libraries, so, the library usage will be easier for designers
Keep the same library analytics
Custom plugin will relink instances to original styles (current files where Themer was used have deprecated styles)
Avoid Figma Swap workaround from old libraries to new one
Force teams to update
Cons:
Breaking changes for teams that want to migrate to new version
Themer wow will be deprecated and teams can't use it (if they update libraries)
Custom plugin to help team in the migration, possible unstabilities and bugs.
Teams that not update can continue using Themer but new instances will need variables, so this kind of teams will work with the old and the new wow. (Themer + Variable)
Duplicate current library doesn't fix the problem with styles changed by Themer, so this strategy is not very profitable
Question to solve
We will include variable for mobile and desktop in a separated way
https://www.tldraw.com/ro/-Bo9IPzJxV4d3fOHscjPj?v=-838,-1351,5498,2833&p=page
Nice to have:
The text was updated successfully, but these errors were encountered: