If we want to support scaling, we need to have the assets scaled before importing, so they're always sharp. Then, you could work in @1x, @2x, @3x, and we can import it at whatever scale you'd like.
That's a neat approach, and having an exportScale parameter for framerExport would solve this beautifully. I did a quick check of the code and it seems to be a trivial change.
If we want to support scaling, we need to have the assets scaled before importing, so they're always sharp. Then, you could work in @1x, @2x, @3x, and we can import it at whatever scale you'd like.