Senjaz

I can't think of a single example where a small dev was acquired by a big one, such as has happened here, where the big dev didn't screw existing users and fans within months of the deal being signed. The play book is so clear that is why we're all being so vocal about it here. Maybe some suit in Australia will get the message and offer reasonably priced perpetual licenses in addition to the subscription option we all know is coming. That's the best possible outcome we can hope for. I'll keep using Affinity as long as that is the case. When a corporation is willing to throw that amount of money at you, it's very hard to say no. There are few that could honestly say they wouldn't take the money. We are all expecting this to follow the pattern: Tell everyone this is great news for the business and customers (but mostly the owners wallets) Reassure users: Nothing is changing (yet). There are no plans to screw our existing customers (it will take us at least a week to write those plans) Offer a crippled version of the product under the old terms, to get the full new version a subscription plan is required. Our customers overwhelmingly didn't like paying for our crippled option, so we're cancelling it. The sad fact is that as soon as the deal is signed any assurances the original owners were given about the direction the company will take are worthless. With almost equal frequency we see founders leave their acquired companies to set up a new studio again to regain creative freedom. One of the other things I love about Affinity as it is now is that the suite is optimised for all the platforms it exists on. It uses Apple's modern APIs to get good performance and a good UI. Only small devs which are passionate about their product do this sort of thing. Big ones always prioritise as big a shared code base as possible to minimise effort and maximise profit. The result is a product that isn't the best it can be on any of the platforms it exists on.

Add me to the list who will drop Affinity like a hot potato if Canva turn it into a subscription model. I don't care how good the software is. The transition from Adobe to Affinity apps wasn't without pain but I did it on principle. I will do the same again.

I managed to get my in-app purchase to activate by attempting to purchase again, when I tried this the app recognised that I had already bought it and showed the activation screen instead of asking to verify the purchase information. I hope this helps others who are having the same problem.

Well I downloaded Publisher 2 from the Mac App Store, purchased a universal license through in-app purchasing and Publisher 2 has not recognised that it has been purchased. It was not done automatically at all. Since the guidance for unlocking the other apps requires the first one to be activated and logged in to the serif account it is also not possible to unlock the others. The "Restore Purchases" link at the bottom of the licensing panel does not do anything.

So Apple added Javascript OSA support without me even noticing. Guess I've been using the same scripts that just work for a very long time. One thing I like about Affinity is that they don't just go for the lowest common denominator for the platforms they support. They produce first class mac applications that use the appropriate technology on the platform – look at their home page which show cases all the Apple technologies they use: Grand Central Dispatch, Core Graphics, Force Touch, Retina UI, iCloud Drive, Metal 2, DCI-P3 panel support. When they ported Designer to Windows, it wasn't just a normal port, they made sure it used current Windows development best practice too. This gives me hope that they will indeed support OSA on macOS.

No no no, it must be OSA (Open Scripting Arcitecture) I don't think there is a Javascript OSA language plug-in any more although it remains possible, currently the only supported language is AppleScript. But any Affinity Publisher scripting absolutely needs to hook into the Apple Event system and hence OSA. This is the only way you can have cross application scripting which is paramount. While I have no love for the AppleScript syntax the workflows it enables save hundreds if not thousands of hours of effort. If Affinity's idea of scripting support is something that only works in their curated garden like VBA in Windows then it will never replace existing tools for mac based publisher workflows. If you want Javascript then resurrect the work done by Late Night Software (https://latenightsw.com) in producing an OSA plug-in for the language.

It's probably been mentioned before in this huge thread.... Please include scripting support. Designer and Photo don't support it, but scripting support in those is of less use. I need to be able to pull in entries from a Postgres data base and format them on a page. Ideally grabbing a template from within a publisher document, replicating it and tailoring it. If this is not done then.... Please make the file format XML based and document it. Consider using the macOS bundle format to package up an XML file and all embedded assets. If this isn't a good idea with Windows then consider just zipping up the whole thing into a single archive. Thank you