Pšenda

I think @loukash meant really "other feedback", not other social media. See part about CAD and Architecture firms.
 

That is your opinion which of course you are entitled to, but you haven’t considered users that prefer and need the current implementation in Aph. You state you don’t want any time or money wasted then fine, leave it alone completely. The 3 apps have different functions, they do not all need to have the same defaults. 

I would definitely take the Win/Mac/iPad platforms into account as well, because they themselves bring big differences in using and accessing applications - especially in understanding what is standard, how to control what, etc...

For example, because I have the tools arranged as much as possible in all applications - which does not correspond at all to my needs for a default tool.
Merging functions/features like layout of tools for the best possible workflow, and some sideefect (that it's also the default tool) is just the wrong way to do it. If it is necessary to define a default tool, then let this option be in the Preferences.

As noted, I have at first misread your post, and deleted the content in the meantime.
You're right, I'm wrong.
Peace! 

For example, because I have the tools arranged as much as possible in all applications - which does not correspond at all to my needs for a default tool.
Merging functions/features like layout of tools for the best possible workflow, and some sideefect (that it's also the default tool) is just the wrong way to do it. If it is necessary to define a default tool, then let this option be in the Preferences.

Or in Customize Tools... dialog, where the choice made can be displayed.

Perhaps it's just me, but I can fully follow the idea why the Hand tool is default in APh, and why the Move tool would be the wrong choice in the app context:
The likely typical workflow for the vast majority of APh users would be opening a bitmap image and look at it first. The Hand tool context toolbar displays a brief summary of the image: dimensions, color mode, profile, camera data. This is a Very Good Thing™. Then a user may perhaps zoom in (I do by using two-finger pinch on the trackpad) and look at a couple of details without accidentally changing anything on the image itself via clicks or dragging. In other words, the Hand tool is the perfect "safety net" to just view images without accidentally modifying them. (Yep, APh sometimes has certain benefits as an image viewer over, say, Preview.app on Mac.)
Whereas with the Move tool active, the standard image layer in the above scenario behaves like a "smart object", being directly editable in the way vector objects are. This is usually not the first thing that I, or one, would ever want to do with a bitmap image, isn't it?
If I had a choice for a "default 'secondary' tool" in APh, then it likely would be the Rectangular Marquee tool. This is what makes sense in the context of the app.

i would hate to see a tool become the default simply because it was the top (top left if one is using more than one column?) tool in the panel. I have the Tools panel arranged how I like it & do not want to have to worry if for whatever reason I wanted any particular tool to be the top left one without it becoming the default.
??? So do all the Affinity apps. For instance, hide the Tools panel & open a document. The default View Tool will be selected. Now press B, P, etc. In fact, hide the entire UI with the Tab key. You can still change to any tool that has a shortcut, right?

IMO, as long as the context toolbar and/or tool cursor in the workspace make it clear which tool is selected then it should not matter that it is not shown or highlighted in the Tools panel.
Besides, as @Pšenda pointed out, the panel may be hidden or a hidden tool may be selected via a keyboard shortcut.

Since you didn't specify which version you were interested in, a link to the base/original version was apparently provided, saying that it is very easy - note the number 2 in the link, to edit the link for version 2.
https://affinity.help/publisher2/en-US.lproj/pages/Media/pictureFrames.html

Personally, I consider Personas, with the help of which I can organize the functions of the application and its working environment (Tools panel and Studios) according to the type of work I am currently doing with it, to be an excellent solution.
So I can imagine that Serif would offer the following 4 products:
- APhoto application, that would work like the existing APhoto, when switching to other applications using the command Edit in...
- ADesigner application, that would work like the existing ADesigner, when switching to other applications using the command Edit in...
- APublisher application, which, unlike the existing APublisher, would work like the existing APhoto or ADesigner, when switching to other applications using the command Edit in...
- ASuite application/package, that would firstly contain a set of all three separate applications, in which you would switch to other applications using the standard Edit in... command, and would also make available "all" Personas of individual applications using StudioLink technology - that is, Publisher/Designer/Photo persona, but also Develop, Liguify, Tone map and especially Export persona.
Thus, a one-man/universal application would be created as another product (using the existing principles that have been working and used for years), where the need for switching and thus complicating the workflow would be minimized. And of course, the need of other users for individual/separate applications would also be satisfied.
Of course, I'm talking about the technical aspect, not the business point of view, when it would be up to Serif's strategy how to take the given products into account and offer a price advantage for application grouping, whether to enable the more advantageous purchase of additional applications to ASuite, etc.

Do you think that it's weird, if you use a keyboard shortcut for a tool - which you don't currently have displayed on the Tools panel (the entire Tool panel can be hidden), that this tool will be activated?

Maybe it's time for a feauture request? It seems to me that this is a behaviour since V1.
 

Because you probably installed a "sandboxed" MSIX version. If you don't like this type, try the MSI/EXE version.
This has been mentioned many times here on the forum, so try searching for detailed information.
For example:
 
 
 

Try Liquify Persona.
https://affinity.help/photo/English.lproj/pages/LiquifyPersona/liquify.html

Everyone is entitled to their opinion, and you’re not the only person to suggest having one piece of software to do everything. But, what about the people who don’t want or need all three apps? If they just want to edit photos, or produce illustrations, why would they want one big app that is full of functions that they might just find confusing and why would they want to pay for it?
I really don’t see much advantage in one app, rather than the three integrated ones that we have now. It obviously depends on how you work, but I tend to do a job in one app at a time, I rarely need to keep changing from one app to another. If I do need to do so StudioLink and “open in” work perfectly well.

Welcome to the forums @Jon Duerr
A quick forum search for default export folder shows that this sort of thing has already been requested more than once, going back to at least 2016:
https://forum.affinity.serif.com/index.php?/topic/17825-default-location-for-save-as-and-export/
https://forum.affinity.serif.com/index.php?/topic/98477-file-default-save-as-export-save-as-in-source-folder/
https://forum.affinity.serif.com/index.php?/topic/197302-export-persona-—-option-to-set-up-default-pathfolder-location-where-exported-files-will-be-placed/
etc. etc.

There are so many really good (even better) Alternatives to Adobe Video Products.
I prefer if Serif continues to focus on the existing products. There is much room from improvement

If the object's fill is opaque, a workaround is to use a centre-aligned stroke with Order set to 'Draw stroke behind'. The inner half of the stroke will be obscured by the fill and so you will need to specify the width as double the amount you want rendered outside of the object.

Perhaps it would be useful to place a point in Help where all types and colors of lines (edges, snapping, dynamic guides, measure, ...) would be listed. Now the user needs to know exactly what they are looking for in order to learn what lines/colors the given function uses. So it's the exact opposite of what the user encounters - he sees something on the screen, doesn't know what it is, and has no way of finding out what it actually is. See also numerous questions - what is that purple/magenta line around my objects? Because he doesn't know that they are Snapping candidates, he can't look at their description in Help, so he doesn't find out - that they have a purple line.

Allow me to be clear: any user is welcome to post here on the Affinity forums.
We do not keep track of our users professional intents, knowledge or experiences.
We openly welcome newcomers and professionals alike to provide their personal opinions and feedback for the Affinity apps - as we are all simply users of the Affinity suite.
No user is greater than another because of their personal experiences or professional history.
Every retail customer pays the same amount for an Affinity license, and therefore all are equal users, who all have the equal right to voice their thoughts and feelings when using the Affinity apps.
I ask that you stop insinuating, or directly referring to other users experiences, knowledge or professional qualities. This is not for you to judge here on the Affinity Forums, and should not minimise or belittle another users wishes or intents for the Affinity apps.
This forum is not a commune, it is a website owned by a private company, where the Affinity team controls the rules by which you all must abide.
If you do not like following our rules, we ask that you do not post to the forums. Continued or flagrant breaking of these rules will result in forum membership being terminated.
Much akin to other users, we welcome your feedback and criticism of the Affinity apps.
We do not welcome direct criticism of other users, or of their personal feedback.
It is not for our users to decide what is right or wrong for other users to post, or suggest for the Affinity apps - though of course you are welcome to voice your disagreement with their suggestions, should it negatively impact your workflow or if other potential options may improve their original idea, for example.
We are not looking to create an exclusionary, homogenous group - but we are looking to create a safe space for all Affinity users.
This thread was started by a relatively new user to the forums, who has every right to share their feedback when using the Affinity apps, and request changes they'd like to see in the app.
Personally, I feel Erno is deserved of an apology - as their thread was overtaken with discussions not related to their feedback, partly not even directly related to the Affinity apps themselves.
I'm sorry that after sharing their feedback and engaging with other users about their workflows, that the thread was overrun with such negativity and personal criticisms.
This is not what the Affinity forums are designed for, and will not be tolerated further.
Again, this is not to say that criticism of the Affinity apps is not valid or welcome here, but we do ask that the criticism remains constructive and threads remain on-topic.
If you wish to discuss the hiring practices of the Affinity team, the design decisions made by the developers or our marketing teams campaigns for how the app is sold - then you should begin your own thread on the subject.
Other users, and the Affinity team, may even be willing to engage in conversation regarding your points raised.
Brigading on another users thread, not related to the above meta commentary, is unhelpful and in my opinion leaves a bad impression on the original poster of the feedback/question - who likely wanted to provide their valued feedback to help improve the Affinity apps, and not much more.
This bad impression might not only cause this user not to return to the forums, but also may dissuade users from posting in the future - neither of which is acceptable in my opinion.
This is why we ask that threads are kept on-topic, so that the user is free to discuss the points they wanted to raise with the Affinity team, or other forum members, in a relaxed and safe environment.
The above does not only go for this thread, or you as a user.
Many threads here on the forums have begun trending in a similar direction as this one, so I wish to make the above very clear to all users of the Forums, new and old.

Most of them will fail here for that image and will remove the middle gray area parts too. Even those who claim to remove checker parts, as far as they just urge from colors and not also from repeated pattern structures.

From the description,
I gather that something other than what was intended was inserted - clicking on the inserted image will not show anything else.

If you look at my previous edited post, the Acrobat extension is causing it for me - the browser itself displays the PDF correctly. Aren't you using something similar in Edge?