bsx

I think it is important and necessary that serif staff create a detailed manual as soon as possible on how to manually transfer all personal settings from the V1 to the V2. I also mean assets brushes and so on.
 

Hello, I am glad to see that Photo 2 can now save WEBP formats. Yesterday I had a lot of images to convert, but unfortunately there is no WEBP format to choose from in the batch job export. The dialog is unchanged from V1, so I went back to using XNVIEW MP. This does a good job.

Hello, I am glad to see that Photo 2 can now save WEBP formats. Yesterday I had a lot of images to convert, but unfortunately there is no WEBP format to choose from in the batch job export. The dialog is unchanged from V1, so I went back to using XNVIEW MP. This does a good job.

I know how you feel.  I have no intention of being Adobe'd a second time.  No subscription and no Internet activation is why I switched to Affinity v1 in the first place.

Hi Mike, thank you for responding so quickly to my suggestions for improving Affinity Puplisher,
but unfortunately they are just descriptions of "workarounds" we all know already.
But great that you are doing this.
 
All following answers are not meant personally but directed to Serif!
To point 1.)
who understands the frame as a fixed part of a layout and sees it in its format and position as a "default" is only shabbily rewarded by the current workarounds.It is important as a creative to be able to work freely and therefore there simply must be a handle, where I can touch and scale the image "in" the frame from any side.
This is a "must" for fast, effective work.
Why should we do this in a palette instead of a short simple Shortcut key (alt key or whatever)?
 
Regarding point 2.)
Basically you can do it this way, but the problem is - after the action "scale to max fit" the frame has a new configuration and this configuration brings consequences that are restrictive and completely disrupt the workflow you had before with this frame.
To prevent this, you then have to reconfigure the frame again and click "None" at the bottom.
This brings us back to the same "Affinity Publisher problem": restrictive, cumbersome, time-consuming.
 
Dear developers of Serif:
let us work freely, as we have been doing for years in other design programs
and don't be so restrictive. You don't have to reinvent the world anymore, you can only improve it.
 
P.S. in the forum there are several who also describe this problem

I've recently completed some large projects (including a 264-page catalog with over 700 images) with Publisher 1.10.5 and 1.10.6 on Windows 10, trying to work around the known issues. That worked very well and I was able to complete all projects in a good time. Adobe is not an alternative for me. I work alone and can import templates or third-party work as IDML.
Serif should give the V2 buyers access to the stable 1.10.6 release for work. And give us a way to import V2 files into V1. Maybe also via IDML.

I've recently completed some large projects (including a 264-page catalog with over 700 images) with Publisher 1.10.5 and 1.10.6 on Windows 10, trying to work around the known issues. That worked very well and I was able to complete all projects in a good time. Adobe is not an alternative for me. I work alone and can import templates or third-party work as IDML.
Serif should give the V2 buyers access to the stable 1.10.6 release for work. And give us a way to import V2 files into V1. Maybe also via IDML.

I've recently completed some large projects (including a 264-page catalog with over 700 images) with Publisher 1.10.5 and 1.10.6 on Windows 10, trying to work around the known issues. That worked very well and I was able to complete all projects in a good time. Adobe is not an alternative for me. I work alone and can import templates or third-party work as IDML.
Serif should give the V2 buyers access to the stable 1.10.6 release for work. And give us a way to import V2 files into V1. Maybe also via IDML.

I've recently completed some large projects (including a 264-page catalog with over 700 images) with Publisher 1.10.5 and 1.10.6 on Windows 10, trying to work around the known issues. That worked very well and I was able to complete all projects in a good time. Adobe is not an alternative for me. I work alone and can import templates or third-party work as IDML.
Serif should give the V2 buyers access to the stable 1.10.6 release for work. And give us a way to import V2 files into V1. Maybe also via IDML.

I've recently completed some large projects (including a 264-page catalog with over 700 images) with Publisher 1.10.5 and 1.10.6 on Windows 10, trying to work around the known issues. That worked very well and I was able to complete all projects in a good time. Adobe is not an alternative for me. I work alone and can import templates or third-party work as IDML.
Serif should give the V2 buyers access to the stable 1.10.6 release for work. And give us a way to import V2 files into V1. Maybe also via IDML.

Hello Leight,
I have now tested it again and today I can not reproduce the crash in Publisher V 1.10.6 on my computer.  
I think, there was no problem with the font selection.
When I opening a publisher file, the program reported missing resources. I wanted to sort in the resource manager to the status - in this moment Publisher crashes.
I will continue to monitor the problem and report it here.
I have just tested it with V2 (loaded the V1 files and performed some actions). V2 Publisher did not crash in this test.

I think this thread about communication is an important one. I don't get the feeling that Serif moderators really read the the posts in a meaningful way to sort the wheat from the chaff and reply to the posts that address really important concerns.
I have been posting for years and never once have I had a reply from a moderator addressing my concerns.
I must make a very clear distinction here between things that it would be nice to have (trace in Designer eg) but are easily realised by third party apps and trivial issues (UI concerns, colours of icons, etc) that an be lived with, and things that make Publisher unusable for professionals (no flowing tables, no text to table/table to text, no column span). 
There has been much sneering in some posts about using the word "professional". Let me explain. I'm a professional but that doesn't mean I'm better than you. It means I derive all or some of my income from using DTP software. So let me give you a real life example of why I can't use Publisher yet and have to keep subscribing to Adobe InDesign. Last week a client sent me a 16 page catalogue to design. The items in the catalogue with their specs and prices, were in a Word table. In InDesign I imported the table and it flows across the pages, simple. If (when!) the client sends me an extra line to add near the front of the table, everything will flow through and adjust. I also publish a monthly magazine with a calendar, usually spanning 3 or 4 pages, sent in a table format – same issues. These are is just not possible to do in Publisher in a way that makes economic sense. This is not some arcane or idiosyncratic feature that only a few people want. This is essential. Yet over the years I have never had any one from Serif acknowledge this and reply with a "we're never going to do this" or a "It's on our roadmap coming soon", and I am certain they won't now.
Why do I bother? Because I'm old school, I was in at the beginning of WP and DTP and later the internet and still believe in helping worthwhile projects. I have said many times that there is much that is excellent about the Affinity Suite (I use Designer and Photo all the time), hats off to Serif. Which is why it is all the more frustrating that there is this blind spot with Publisher - it's like watching a loved son or daughter making some poor decisions in life and feeling powerless to help.

Many thanks to @lacerto. 😀😀😀
You have saved me.
Because I can not use the V2 programs at the moment (I paid for them), so I continue to use V1 for work. yesterday @lacerto's solution saved me. Publisher 1.10.5 (Windows 10 22H2 all updates up to date) crashed on every action changing Preflight Profiles. I have many Preflight Comments in a large project and could no longer access them.
I found the solution recommended by the Affinity team to uninstall 9 Windows Updates not very professional and I hope there will be a solution here soon as the bug has been known for a very long time.  
I can recommend the solution from lacerto. Publisher V1 has not crashed since the change. I have saved the original Publisher.exe.config file and can go back at any time.
 

I do not think that we really know whose "fault" the recent crashes and anomalies with e.g. fonts, linked resource and profile lists (the latter in Affinity Photo only) are, but we know that after installation of a recent update to .NET 3.5 and 4.8 (and 4.8.1) these errors do happen with Affinity apps (and most probably with other, too, that have enabled data virtualization in context of list controls), both on Windows 10 and 11.
There is a known, easy workaround to disable the functionality that causes these issues in apps that use WPF based user interface and controls. Those users of Affinity apps that choose to keep the recent .NET 3.5 and 4.8.1 by default automatically applied recommended system updates (instead of rolling them back to avoid these rather limited Affinity-affected issues), might want to apply the easy fix given in this post to keep the updates and also avoid the issues caused by them.
If you decide to try this, please understand that you do it “on your own risk” so the instructions presented here are given just as user-to-user tip in a situation where Serif support has chosen to recommend unrolling of a recommended Windows update (that also contains security fixes), instead of giving detailed information of the problem. IMO, users who choose to unroll a security related system update also do it “on their own risk”, but most of them probably inadvertently, unless they have read the KB article related to the update they are advised to uninstall. Personally I’d definitely keep all the system (security) updates (and keep on receiving further Windows updates, rather than taking a risk of blocking miscellaneous new updates because of having unrolled one possibly being a pre-requisite for further recommended and automatic fixes).
I have no competence of making statements on whether these updates, which in addition to security fixes also contain several improvements that make the affected controls more stable, also have changes that are themselves directly causing new issues (that is, if they contain clear bugs), or whether the fixes are such that they break apps that have used certain features that in the improved versions require handling and processing, but omission of which did not cause problems in earlier versions. So far Microsoft has not provided any further fixes to the affected .NET modules, and the KB articles related to these updates state that MS is not aware of any issues related to applying these recommended updates. As far as I know this is the latest KB article related to Windows 11:
https://support.microsoft.com/en-us/topic/october-11-2022-kb5017271-cumulative-update-for-net-framework-3-5-and-4-8-1-for-windows-11-version-22h2-535ac8db-c89b-43f7-abd7-a3c3240320e6
It is quite possible that such issues exist and that there will be an official fix some time in the future, but as long as such information is not made public to users (either by MS or Serif), I think that for most users it is best to allow recommended system updates and just try to live with the app issues for the moment (until getting more detailed information), as they seem to be such that can easily be either avoided or worked around (the issue with linked resources is more serious, however, and if not attended, can make it practically impossible to work with the project).
Anyway, those who don’t mind fiddling with the app setting text files and making a couple of tiny changes in them to avoid the .NET 4.8 update related issues in Affinity apps, can choose to do the following:
NOTE: You should make these changes only if you have .NET 4.8 (or a sub version like 4.8.1) installed due to recent Windows update. Please check the update history to see that this is so. Disabling the data virtualization setting has no effect unless you actually have the update active, but then you should not experience the mentioned issues in the first place)
1)      The files to be edited in case you have Serif-store purchased versions are:
C:\Program Files\Affinity\Publisher\ Publisher.exe.config
C:\Program Files\Affinity\Designer\ Designer.exe.config
C:\Program Files\Affinity\Photo\ Photo.exe.config
In case you have Microsoft Store purchased apps, I am not sure if it is wise or even possible to tamper with the configuration files, even if their location can easily be revealed by using Task Manager and opening the location of running Affinity executables.
2)      The changes to be made in each of these text files are the following:
a) In line that states the sub version of the .NET runtime version, enter 4.8 instead of 4.7.2 or something else that states the current version:
    <startup>
      <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8"/>
    </startup>
b) In line that states whether data virtualization should be used in context of list controls, change the current value from “true” to “false”, as follows (alternatively you could delete all three lines, that is, the <appSetting> block, but it is enough to just set the value of the only setting in this block false):
  <appSettings>
    <add key="IsVirtualizingStackPanel_45Compatible" value="false"/>
  </appSettings>
3)      Save the changes (you need to run your text editor in Administrator mode), then launch your Affinity apps to see if this has fixed the problems with font lists (any Affinity app) and color profile conversion (Affinity Photo).
I cannot tell whether changing the runtime version number can have any negative effects, but if so, then it is easy enough to cancel the changes and revert the original settings. For that purpose it is a good idea to make backups of the original setup configurations before making changes to them.
I hope this user-based help is considered acceptable on the forum. I am giving it basically because I find it disturbing that Serif support currently appears to advise users to uninstall security involved recommended updates also related to issues the cause of which is not necessarily the mentioned system update, basically just to see if it “could be”, making users of release products kinds of testers (instead of spending some time and examining the cases themselves) -- and without giving any further details of the nature of the updates that they ask users to uninstall (exact KB numbers are not given, either, and e.g. there are already four or five 3.5. and 4.8 updates for Windows 11, and additionally feature updates that might either include them or be blocked because of being dependent on them).
Instead, it is basically implied that the update in question is a Microsoft blunder that the users should get rid of in order to make their system operable again [UPDATE: or, that because the issue has arisen spontaneously after a system update, it is a responsibility of MS to fix the problem as if Serif were not in power of doing anything to the matter themselves]. No notice is given whether the alleged “bug” is actually acknowledged by MS so that a fixed update could be expected in due time, or whether users of Affinity apps should permanently avoid Windows updates involving .NET components, whether security related or not.
I have not seen any publicly given information on whether a kind of feature-disablement fix (or “workaround”) shown above might at some time point be provided officially by Serif, as well, in an event it seems that there will be no Microsoft provided update that one way or another manages to implement the made improvements and security fixes without causing breaking of existing apps. And whether it is provided for all 1.x versions since they all seem to be affected.
In case this information is considered inappropriate to exist on the user forum and is estimated to possibly cause more harm than good, I apologize for posting it, and hope the moderators will remove it. The intention was nevertheless good, and due warnings were given.
UPDATE: The latest Microsoft cumulative update as of October 25 to .NET 3.5, 4.8 and 4.8.1 still does not seem to fix the issue (tested on Windows 10 and 11), and in the release article MS still claims their view of not being aware of any issues related to the update:
https://support.microsoft.com/en-us/topic/october-25-2022-kb5018341-cumulative-update-preview-for-net-framework-3-5-and-4-8-1-for-windows-11-version-22h2-6bb1451c-7782-4a1f-bfdf-31140d49ee99
It means that this problem has now lasted already over a month (and the modules causing this problem in Affinity apps have been re-distributed already in a number of different cumulative updates, some containing security related fixes, as well). I do not know if rolling back the update could cause delay in update of any feature, quality and security updates but e.g. on my Windows 11 computer there is one feature update and eleven Windows 11 related quality and security updates that have been auto-installed after September 17, when the modules causing this issue were first time installed on this computer. The next official monthly cumulative update will happen on Tuesday Nov 8, and if this will not fix the issue, I would be a bit worried about the status of the problem (as there is a chance that there will be no auto-fix to the problem from MS). 
UPDATE2: For me, the patch Tuesday update as of Nov 8 2022, also including (once again) an updated .NET 3.5 and 4.8.1 module (in addition to making several other system updates), unfortunately did not bring a fix to the issues experienced in Affinity apps because of changes affecting WPF data virtualization, so the above mentioned fix is still necessary, if you choose to keep Microsoft updates.
The release note of the latest .NET 3.5 and 4.8.1 update for Windows 11, 22H2, also including a security fix: 
https://support.microsoft.com/en-us/topic/november-8-2022-kb5020622-cumulative-update-for-net-framework-3-5-and-4-8-1-for-windows-11-version-22h2-b28f2daf-af6d-4182-a960-05c607a27ef5
UPDATE: There is now official 1.10.6 update for Windows that properly fixes this issue. Please use that instead of the workaround. The updated version will overwrite any manual changes made to the app setting file so you do not need to restore anything to get the apps behave as planned.
 

Make a table with the Table tool. Then open the text styles. You will find a style called table body. You have to customize it.

Here is a template for an A4 sized prism desk 2023 calendar created in AD. This template can be (re)used in all Affinity apps!
This 2023 calendar is localized in german, english and greek (DE/EN/GR) and thus allows to switch the calendar languages and print for either language. The calendar dates used in this template do stem from Mensch Mesch. - The ready glued together calendar looks like the following ...

... the A4 Affinity Designer template looks like this, dependent on the language (DE/EN/GR) switch ...

You set and switch the corresponding language like this for the german (DE) calendar part ...

 
.. or like this for english (EN) calendar part ...

 
To add your images into the calendar follow the localized instructions like written onto this shown 2022 calendar variation ...

 
...  here is the corresponding AD template file ...
prism_A4_calendar_en_de_gr_2023.afdesign  
Let's have better times then in 2023!

Hi All,
Well, it’s been a pretty crazy week since the launch of V2!
This has been a real labour of love for us over the last year or so, and I can’t even begin to describe how hard the development team have worked on it. Not only getting the V2 apps launched, but also of course finally bringing Publisher to iPad. 
With this being our first paid-for upgrade there has understandably been a lot of feedback / questions around future updates and our pricing policies. I thought it was worth addressing / clarifying our position on some of these personally...
Updates to V2 moving forward
Buying V2 not only gets you all the new features you have seen, but we have various updates planned – including many more new features and improvements – which you will get for free. This will continue until such a time that V3 is released. We’re not sure exactly when V3 will be, but I can confirm we are not going to move to anything as regular as an annual upgrade cycle as has been speculated.
It’s worth saying too that V2 does include many under-the-hood changes to our underlying technology, and we have also been investing in several new areas of research recently. Some of these haven’t manifested themselves into new features yet, but overall V2 does give us a better platform to develop on moving forward and I’m sure you will be pleased with the updates V2 will receive.
Updates to V1 moving forward
While we did say on the FAQ that V1 would no longer receive any updates, I want to clarify that was about new feature updates. We will be updating V1 to fix any critical problems caused by operating system updates in the future. So if the next version of macOS breaks V1 we will endeavour to fix it. There will be a point in time when continuing to maintain V1 in this way will not be tenable, but certainly for the foreseeable future we will continue to patch. In fact, we have an update to V1 queued up for release very shortly with some fixes for Ventura and issues caused by a recent Windows security / quality update. 
We will update our FAQ shortly to make that clearer for everyone.
Offer period
In case you didn’t see, I’m pleased to confirm we have decided to run this initial launch offer until 14th December to give everyone the best chance possible to get it if they wish / have a decent amount of time to trial it. 
Upgrade pricing
It’s been really hard to see some of the comments about us not looking after our existing customers – we’re pretty devasted that anyone feels like that to be honest. But the fact is we felt our hands were tied somewhat with being able to offer upgrade pricing in a fair way. The main reason for this was App Store customers (which make up around 35% of our userbase). The problems with that are two-fold: firstly, we didn’t have a way from within V1 to validate an App Store purchase receipt to reliably ensure customers who were entitled to an upgrade could get one; and secondly, we could not find a good way for people to get that discount via the App Store. Us pushing upgrade customers to go exclusively via our own site (including customers who were previously acquired via the app stores) may also have put us in violation of App Store Ts & Cs which we were obviously concerned about.
I’m not saying that these issues were completely insurmountable, but any solutions we came up with would be messy, and most importantly could have resulted in some bona fide V1 customers struggling to get validated and claim their discount. We certainly don’t have the support resource here if we ended up needing to manually validate tens of thousands of receipts for example.
The only option we felt was safe to move forward with was a general launch offer, which would guarantee that every V1 customer could get the discount, whether they purchased directly through us or the App Stores. We knew a side effect of that would mean some new customers would end up receiving that same discount – but we felt that was a better option than V1 customers missing out. It’s also worth saying that while there has been some good press about V2, all our main marketing has been via email and through social media to our followers. In other words, we felt ok about it because we knew the vast majority of people who would find out about it or take advantage of the offer would be existing customers. I would be surprised if over the offer period customers upgrading from V1 didn’t make up more than 90% of our sales.
Overall I do believe us giving a 40% discount, along with the addition of the new Universal Licence of course, is offering fantastic value for money for those who want to upgrade. 
However, taking on board some of the feedback there is something extra we can do – we will offer a new free bundle of content exclusively for V1 customers upgrading to V2 as an extra thank you for your support. I’ve seen this suggested by a number of customers and it’s a great idea as it does remove the App Store conflict entirely. 
We’ll need a little time to put something together, but all customers who previously registered or purchased V1 and have since upgraded to V2 will receive a voucher code for this via email as soon as we can.
A comment on no subscription
I do want to say that some of the points above are exactly the reason why software companies move to subscription. Whatever you do with upgrade pricing, you still have the issue of customers who bought the previous version 3 months ago vs. those who have had it 2+ years. Offering perpetual licences also gives the additional overhead of needing to maintain the previous version longer than you would if everyone was on subscription / generally always on the latest version.
We are a small team so some of these complications are not ideal — all we really want to do is focus on developing our latest codebase, push out regular updates and continue with our mission to make great creative software accessible to everyone. 
But it does need to be funded somehow. We know you love our no-subscription model, but there also needs to be a level of appreciation that the alternative is having paid-for upgrades from time to time. That unfortunately comes with its own problems.
All of that said, I have to say we have been blown away with the response to V2 - around 3 times as many people have upgraded in the last week than we expected - and we really can't thank you enough for the support you have shown. More than anything the success of this upgrade puts us in a great place to continue investing heavily in development which is ultimately what it's all about, and we’re super excited to crack on with some great updates coming next year!
All the best,
Ash

After Adobe went to subscription-only, I coasted on CS6 for a while and then switched to Affinity, and have never looked back. OK, well, I do fire up Photoshop every now and again for one reason or another, but overall I've been delighted with the Affinity products, and the value proposition they offer.
Market-wise, Serif's products lie in the middle of the huge gulf between expensive, rigid Adobe, and free, freewheeling open-source alternatives (GIMP, Inkscape, Scribus...). With respect to communication with users, I find myself wishing that Serif would lean more toward the behavior of open-source products.
Serif's communication is hit-or-miss. The v1 Beta programs did a good job giving users an insight into short-term plans for features and bug fixes. But this was all users could see in the way of a product roadmap. And the long gap between v1 and v2 with no public Beta left users in the dark for a very long time. For the most part, we were left guessing. Just the fact that there was a thread entitled "Is Affinity dead?" exemplifies that situation.
In the forums, Serif staff are very responsive to questions about bugs, existing features, and product behavior, which is absolutely wonderful.
On the other hand, my perception is that questions about Serif's short- or long-term plans, or even in some cases questions about existing policies, are greeted with a frustrating silence. 
Recent examples include the v1=>v2 upgrade pricing kerfuffles (there are two of them: one for longstanding v1 users, and one for recent v1 purchasers), the Windows msix installation debacle, and the aforementioned radio silence after 1.10.5.
Some of this secrecy might be justifiable (if somewhat cynically) for business reasons. For example, prospective first-time customers looking to buy Affinity v1 this past July might've been discouraged if they knew that v2 would be released in November, but they would have to pay the going rate for the upgrade. Or, if they learned that their hoped-for feature would not be implemented. So they might have chosen to hold off, impacting the timing and amount of revenue to Serif. 
However, for the most part, I am having trouble understanding the rationale for much of the secrecy. Seeing a product roadmap can be an incentive to buy into a product at an early stage. Maybe someone doesn't want to purchase Designer because they're not sure if there'll ever be a bitmap trace feature. If they see it on the roadmap, perhaps they'll take the plunge now, to start their transition. 
And most of us understand that there will be uncertainty. Even without a definitive answer, a response is superior to silence.
It's fine for Serif to say, "This is the fairly firm roadmap for v2.2 through v2.3, the tentative roadmap for 2.4-2.8, and the speculative feature set for v3. Any of this is still liable to change. Feedback welcome."
It would have been fine for Serif to say on the day after the v2 announcement, "We understand that some users have an issue with the MSIX installation. We're going to be discussing it among ourselves to determine what, if anything we will do in response. Stay tuned." It obviously would have been even better if the plans to use MSIX had been divulged months before announcement, since it would have better prepared Serif for release.
Posts like Ash's, which explain details surrounding the pricing and upgrade decisions, are fantastic, but IMO they could've been published MUCH earlier.
Most of the people who follow the forums, myself included, are committed Affinity users and supporters. We're going to be upgrading to v2, and we're very likely to pay again for v3. So I'm just not clear on what Serif gains by being so reticent to tell us what's going on, and what the plans are for the future.

Many Thanks. That's exactly my opinion too.
I think the communication of such major system changes must take place BEFORE. And not just discovered by users during installation. 😡

Yes, we will be providing MSI installers to customers who require them. This FAQ will be updated with links to MSI downloads when they become available.
Yes. These are now available
 

This news will also help some in this thread

Hi all. Thanks for your patience over the weekend when our offices were closed.
We've had a meeting this morning and decided to ALSO offer MSI installers, to those people who would like them. I can't tell you when this will happen, as there is engineering work that will be required to allow this to happen, but we hope it won't be long.
Thanks for your feedback!

I hope it will be supported for a long time. This is the anwser I was looking for.
I just dont want to get Adobed again with those lazy servers... Protect the software while you support it, but dont punish licence owners.

Personally, I have no problem with dots to indicate Activity and Visibility, I would just suggest using solid and hollow dots to indicate ON and OFF status, not brightness of dots.

Solid/hollow dot is a visually understandable and unambiguous, and also saves space in the Layers panel (thanks for that).

I bought Affinity Suite 2 immediately and was very happy to see this story continue.
But now, I will continue in my projects with V1 in the near future and observe further developments.

Good:

There are really some basic improvements and enhancements that will be very useful in future work. And I'm sure there will also be new developments in V2, which I'm looking forward to.

Bad:

This hype, overstaged by Serif, has not done the reputation of the software any good. Professional users were left completely in uncertainty for months as to whether this software would be further developed, discontinued or completely changed. No roadmap, no info, no beta phase.

Now these unfortunate problems with the app installation, which has irritated many users who now have to realise the workflow with other programmes in workarounds.

Also bad is the online activation requirement, which affects everyone who does not connect their computer to the internet for security reasons. But this will also lead to problems in the future, as we know them from Adobe. Activation servers can no longer be reached after a few years, the purchased software can no longer be used on new hardware.

Conclusion:

It was exactly these advantages of version 1 (no online activation requirement, user-friendly installation, easy integration into existing workflows) that made Affinity programmes attractive to many professional users. In V2 these features are reduced step by step and I think this is not a good way. My enjoyment of new features is very limited as a result.

Wishes:

- Standard installer version

- Backwards compatibility from V2 to V1 (saving under V1 version even with the loss of features)

- IDML export


 
Sorry, my English is bad. Translated with DeepL