
If people want to pay a monthly fee to use a plugin, I have no problem with that. I don't think there is anything wrong with the development team providing the ability to use different plugins with Designer, in fact I think it would be very useful.
#Zeplin design software
I think that implementing something as specific as a "Zeplin" module inside Affinity Designer, with a whole new set of features, would cost some tens of thousands of dollars and would benefit only a portion of their user base. So, why not provide integration to third-party software like Zeplin, which would be far easier to handle and to give support? Meanwhile, the almost sole reason why I hadn't adopted Affinity Designer as my main UI design tool, is precisely because of the lack of features like these.

In my opinion, if you don't see advantages in this request, maybe you should just not endorse it, or maybe just give a better alternative.

So, why not provide integration to third-party software like Zeplin, which would be far easier to handle and to give support? I think that implementing something as specific as a "Zeplin" module inside Affinity Designer, with a whole new set of features, would cost some tens of thousands of dollars and would benefit only a portion of their user base. They made some effort implementing constraints and symbols, but these features are rather limited at the moment. Now, looking at Affinity main features and roadmap, we can tell that they are more focused on illustration than on UI design. So it does not add extra costs to my budget. I freelance for companies which usually pay for Zeplin licenses because the content hosted there is their own property, while the software I use (Affinity, Sketch) is my property. Platforms like Zeplin have a very specific purpose: allow people to review files and get assets, without the need to install and learn specialized design software (which requires buying more licenses). This saves hours and maybe days of unnecessary work. Solutions like Zeplin allow you to, with a single click, upload the whole file to a system that can be accessed by many people (mainly stakeholders and developers), where they can check automatically generated specifications and exportable assets (icons in png, svg, etc), with color swatches, font styles, etc.

Once you design a UI, you have to deliver it to developers, in a way they are able to implement the front end as closest as possible to design specifications. I'll try to best clarify the need to integrate to Zeplin or other third-party solutions for development handover (at least based on my daily experiences working as a UX Designer). Now you have the opportunity to use quality, non-rented software like Designer and Photo and you are asking to be able to add subscription plugins to it? No thanks. You have to rent your software from Adobe or the makers of Sketch (no thanks) and then you have to rent your plugins too? Where does it end?

I've never understood the appeal of plugins like Zeplin (which is a subscription service).
