[Shape export to Apples Motion]

I just moved over to Pixelmator Pro because of the Motion project export. I've owned it almost as long as Affinity but haven't used it much until I heard about the Motion Project Export feature they recently added. The text export is not the greatest (I find any custom leading ends up having to be reset in Motion) and the text tools in Pixelmator are limited but - I get editable text (and thus can apply Motion's text behaviors to it) and my layout stays intact and doesn't have to be rebuilt. With Affinity I was exporting my layers and then rebuilding my layout in Motion. I'd prefer to stay with Designer - It's been my go to for the simple graphics I do for low budget TV ads ever since I dropped Adobe. I just now tried the SVG export from Affinity to Pixelmator import and it kept my layout but broke my text to different layers (still editable text but one line would be on four layers.) so, dang! I'll end up spending as much time fixing that as fiddling with Pixelmator's text tools. Anyway, I up vote this as well it would solve my biggest issue with Designer ... that and the lack editable text in PSD exports so I can send my clients Photoshop files in which they can change the text. Yes, that's another topic and I have my request in there but it came to mind as Pixelmator does this as well. I'm not a Pixelmator fanboy it seems clunky to me but it does a couple of things I find useful so I'll have to learn it and just keep hoping Affinity finds a way to implement these two things - Motion Export being a higher priority for me.

[Save PSD files with editable text, not rasterized text layers.]

I found that Pixelmator Pro ($40 non-subscription) will save out Photoshop files with editable text files or at least it did a while back ... This doesn't solve my work flow preference of working between Designer and Photo but it's a non-subscription alternative. While I assume it's still capable of this I can no longer test that the Text remains editable in Photoshop (I quit my Adobe subscription a few months ago when my client no longer needed photoshop files ) but I just checked and it is editable when I bring its Photoshop export into Designer. Anyway I have become accustomed to using Affinity and would like for editable text files to be a feature so I don't have to fumble around in unfamiliar software just to be able to send a client a file they can edit with Photoshop. I've attached a simple test psd exported from Pixelmator Pro incase someone wants to test it with Photoshop.

PixelmatorProPSEditableTextTest.psd

[Save PSD files with editable text, not rasterized text layers.]

+1 Had to re-subscribe to Photoshop because I acquired a client who needed psd files with editable text. I'd jumped completely off the Adobe plan almost 3 years ago. Now, when I'm working on his projects I miss my Affinity workflow between Photo and Designer for adding Call-outs and other graphics to photos. Studio Link looks to improve this workflow even more ... and now, arrowheads ... Arrrgh! And then to add to my frustration I'm playing with Procreate and it's newly added text feature and see that it exports psd files with editable text (but, alas, it has no real vector tools or full feature photo editing but ... editable text ...yes). I love the 1.7 release, and look forward to using the Studio Link buttons and other features just rolled out on my work for most of my other clients. But please save me the subscription and pain of having to switch to working with Photoshop's rudimentary vector tools next year by making editable text available in psd exports as quickly as possible across all platforms.Yes, your pricing is such that after jumping off the Adobe subscription I could afford to put both of your apps on all three of my devices. 

[Can't open Affinity Photo Document created on ipad with my mac]

I created a new document using Affinity Photo on my ipad and saved to my Dropbox. When I tried to open it on my iMac (Affinity Photo 1.5.2 and I also tried it in Affinity Design 1.5.5) I got an error message that it was created in a "newer version" and couldn't be opened.