tiiimo

Anyone can download the software. Without a product key it will only run in Trial mode.
With a product key you can turn it into a standard retail version, but you also need to know the email address that it was originally purchased with, as that is another part of the registration process that cannot be changed.

Hi Tiimo,
Welcome to the forums
I believe this is being caused by the layer shown in my attached screenshot it doesn't quite stretch to the bottom of the canvas. If you drag the bottom handle down a tiny bit so it covers the canvas your file should look fine upon export.
Thanks
C

The title says it, you might already be aware of this, currently you can not set the starting color with the color picker tool when using a HSL Adjustment. (You can in the Desktop Version though)

I have found that sometimes when in the develop module the image all of a sudden switches to the photo mode as if I had pressed the develop button, which, to my knowledge I haven’t.  Very annoying. Maybe this is also what is happening to you. 
 

Hi Madmac09,
It's not currently in the iPad version of Designer.  We do have this logged with the Dev team and i'll bump that report  

Hi @Dave92029, welcome to the forums!
It sounds like you are not part of the target market for the Affinity products, though I suspect you probably meant to post this in the feedback section for Affinity Photo rather than Affinity Designer?

Try Color filters, Erase White Paper.
Alternatively, try Refine Selection.
https://affinity.help/photo/English.lproj/pages/Selections/selections_refine.html

Yes.  Thanks.  Good to know.  The more things like that I encounter the more impressed I am with this app.

AP allows me to open files so large that PS refuses to open them. RAM usage is much better.

A bit ironic that you said "prime time." One of the several reasons I enjoy using AP is the responsiveness of the app, particularly for panning & zooming quickly with no stuttering, previewing filter effects & layer modes in near realtime, & the like. For me, this is where time is my prime concern, & where I find other apps lacking.
 
For that I will gladly live with larger file sizes.

Just to go into a little more detail about what we do.
 
Our data format has to preserve pixel accuracy. What you edit has to be retrieved exactly after reopening your file. We do use compression when saving raster/pixel data, but it is lossless compression.  As such it does not compress with as high a ratio of other lossy forms (such as JPEG).  JPEG will always distort pixel values, and with higher compression ratios it also introduces visible artefacts.  Many people can live with this in the end file (to be used for web or print), but would not want it during sequential editing.
 
We did some research into the balance of compression processing time against size reduction and hit upon what we felt was the best ratio for general needs.  The reality is that using common compression methods there is a sweet spot, after which the increased processing overhead (and consequently time) yields smaller and smaller returns in size improvement. In a typical test we found that in order to achieve just 3-5% more compression, it could take twice as long to compress.
 
The problem with using lossy compression becomes apparent in sequential edit-save cycles where the artefacts caused by lossy compression will be compounded, making the image worse with each edit and save.
 
You will find the same effect when using Photoshop - the PSD format also uses lossless compression.  Open a heavily compressed JPEG and save it as a PSD, and you will see a massive difference in file size.  This is not uncommon or unexpected.
 
Affinity files will be larger than PSD files, however, as we order our data in a way that provides fast incremental saving and loading times.  This is something that should be apparent when comparing the two formats.  It allows our files to be much more scalable without the massive overhead involved. Since our saves are incremental we don't have to create the entire file every time we save.  This also means that auto-backup happens largely without you noticing it.

It has been mentioned many times that the native Affinity file format is optimized for performance, not for file size. This includes pre-rendered views, various kinds of metadata, & other stuff they are not willing to go into detail about, some of which (I assume) enables the unique ability for different Affinity apps to share the same format.
 
Something else to consider is that there are dozens of RAW formats, most of which use some form of data compression (either lossless or lossy), which can increase 'developed' file sizes significantly. The compression is not necessarily optimized for performance, & may be poorly suited for general editing tasks (particularly when live, near realtime updates are desired), which is part of why Affinity sacrifices file size for performance.
 
Also, these days 150 MB or larger image files are not at all unusual. I have dozens of files from a Nikon 12 megapixel point & shoot camera that were saved to PSD format in Photoshop Elements, & they typically weigh in in the 1 to 2 hundred MB range. (Importing them into Affinity Photo & saving them in Affinity native format typically reduces the file size by 10 to 30% or sometimes more, so it is not as if Affinity's native file format is unusually inefficient in this respect.)
 
I realize that these file sizes seem large, but in the greater scheme of things, with typical hard drive capacities now in the ½ to several TB range, relatively speaking they are not -- after all, one TB is equal to one million MB. If your startup drive is a limited capacity SSD or just full of other stuff, that may still be an issue, but it is relatively inexpensive & quite easy to offload most of these large files to a large capacity external drive. Plus, even if access times are slower, Affinity's performance optimization (& efficient memory use) make this much less of an issue than it would be with (for example) Photoshop, which is so memory inefficient that it is often necessary to dedicate a second drive for additional scratch space just for it to be able to handle large image files without choking.
 
The bottom line is, as with so many other things, there is no way to optimize everything at the same time -- it just isn't possible. Affinity's developers chose not to optimize for small native file sizes for very sound reasons. If you must have that, you can export to tiff, but that also has tradeoffs, as will anything else.

I think when 1.7 comes out Affinity users will be like: