Ben

Since this subject comes up often I am writing a definitive statement.
Fireworks (layered) PNG files
There is no such thing as "layered PNG".  The PNG standard does not define a way to store layers, and only deals with flattened images.
Fireworks saves out additional layer data to PNG files in a proprietary format using a private tag. A definition for this proprietary data has never been made public.  A PNG saved by Fireworks can still be used as a flattened image by any application that can handle PNG files.  These applications will handle the standard data and ignore the proprietary Fireworks data.
Affinity handles standard PNG files.  But, it cannot import or export the layer data using the Fireworks method.
There is no expectation that we will ever be able to handle Fireworks layer data in PNG files.
We acknowledge that being able to support Fireworks PNG files would be of great benefit to users of Affinity.  If a public definition of the data format becomes available, we will be able to address the issue.
 
Layered TIFF files
There is no such thing as "layered TIFF".  The TIFF standard only handles flattened images as part of the publicly described tags.
TIFF does allow for companies to register additional tags for their own use. Adobe registered two private TIFF tags that enable them to embed layer data in a TIFF.  These tags are an extension and are not part of the central TIFF standard.  These tags are used to embed PSD layer data into a TIFF, in addition to the standard flattened image.
Since Affinity has a PSD importer, we are able to import the layer data from a TIFF if it has these tags.  However, since this is handled by our PSD importer it is subject to the same limitations as importing a standard PSD into Affinity.  We make clear that while we aim to provide the best third party support for PSD, we can never replicate 100% the way Photoshop handles and displays a PSD file.  Photoshop has its own approach to applying alpha/transparency, vector masks and vector strokes, layer effects and gradients.  This means that while we can offer importing of editable elements of a PSD file, the result will not be a one-to-one pixel reproduction of what you see in Photoshop.
We have registered our own TIFF tags for embedding Affinity layer data in a TIFF, in similar fashion to PSD layer data. This is intended for use with DAMs that use TIFF as their interchange format.  When saving a TIFF file, if your document has multiple layers you will be given the option of including Affinity layer data.  This will preserve the editable elements of a multi-layer document.  This obviously comes at a cost of increased file size.  Our TIFF tags will use our proprietary data format and as such can only be used by Affinity applications.
At this time we have no plans to save TIFF files with the PSD format layer data.  PSD layer data held in a TIFF file will be imported and converted to the Affinity format.

Not sure scripting is the answer to everything....
 
But, we've thought about spirals - just not had time to do anything about it with other more pressing features to write.

It's not an easy feature to implement....

At some point in the future I'll be adding 'live' corners to shapes so that you can corner without having to convert to curves.

It's not an easy feature to implement....

At some point in the future I'll be adding 'live' corners to shapes so that you can corner without having to convert to curves.

Honestly, I don't care about some bugs. The will be fixed over time. This can't be said about Adobe, they permanently add new gimmicky features that 2% of their customers use instead of fixing serious bugs and improving workflows. Instead the do the opposite by shutting down Cloud Extract completely for example. Paying a company a monthly fee for not fixing anything and ignoring customers? No thanks. 
 
I love you all @Serif, can't say it often enough.

There was a "small" bug in the parsing of parenthesis.  Now fixed.
 
Incidentally, we can already do complex functions, and we already offer functions including:
min(a,b )
max(a,b )
mid(a,b )
sq(x)
sqrt(x)
abs(x)
lerp(a,b,t)
clamp(a,min,max)
sin(angle)
cost(angle)
tan(angle)
 
Note: Angle has to be in an angle unit, such as deg or rad.  So, you'd type "sin(45deg)".  I'm looking at the option of promoting un-typed values to the type required by functions (so a number would be promoted to an angle where required).  We are a little strict about types because we allow for values to be expressed in incompatible types, such as percentages, angles and unit distances.
So, you cannot do "5mm + 40deg", for example.

There was a "small" bug in the parsing of parenthesis.  Now fixed.
 
Incidentally, we can already do complex functions, and we already offer functions including:
min(a,b )
max(a,b )
mid(a,b )
sq(x)
sqrt(x)
abs(x)
lerp(a,b,t)
clamp(a,min,max)
sin(angle)
cost(angle)
tan(angle)
 
Note: Angle has to be in an angle unit, such as deg or rad.  So, you'd type "sin(45deg)".  I'm looking at the option of promoting un-typed values to the type required by functions (so a number would be promoted to an angle where required).  We are a little strict about types because we allow for values to be expressed in incompatible types, such as percentages, angles and unit distances.
So, you cannot do "5mm + 40deg", for example.

This will be done in the next round snapping improvements.

@dariobros
 
We've stated it many times before - there is no such thing as "layered PNG" - it is proprietary data inserted into a standard PNG that Fireworks uses. Since that data has no public documentation it is next to impossible to open a PNG with Fireworks data and retrieve the layers (for any app other than Fireworks).  Also, since the Fireworks PNG format was not created by Adobe, we can't use our knowledge of Adobe files formats as a starting point to try decode this data.
 
@CartoonMike
 
There is also no such thing as "layered TIFF" - and it is not in the standard.  What is in the standard are two TIFF tags assigned to Adobe which they use to embed PSD layers into a TIFF, but the content of those tags is not explained in the TIFF standard.  TIFF itself only supports flattened images.  A number of apps can read the Adobe tags from a TIFF, but it is subject to the same PSD import limitations that we always talk about.  The support for layered TIFF is only as good as the support for PSD import, which is a moving goal.  Adobe also has its own methods for applying alpha, layer effects, gradients, etc. These all affect how closely a third party app can replicate a PSD in composition.  I can guarantee that no third party app will produce 100% pixel match for Photoshop if they also support layer effects, vector masks, gradients. PSD doesn't contain a rasterised version of layer effects, so a lot of third party apps cannot import those if they rely on using the rasterised version of layers.
 
We have also registered TIFF tags to allow us to embed Affinity layer data into TIFF files.  So, like with PSD, if your exchange file format for use with a DAM is TIFF, then you can optionally preserve your Affinity layers.
 
Of course, our recommendation is that you stay with a proper Affinity file because that will give you the best performance and file size, and use our export options for creating publication formats.

Since this subject comes up often I am writing a definitive statement.
Fireworks (layered) PNG files
There is no such thing as "layered PNG".  The PNG standard does not define a way to store layers, and only deals with flattened images.
Fireworks saves out additional layer data to PNG files in a proprietary format using a private tag. A definition for this proprietary data has never been made public.  A PNG saved by Fireworks can still be used as a flattened image by any application that can handle PNG files.  These applications will handle the standard data and ignore the proprietary Fireworks data.
Affinity handles standard PNG files.  But, it cannot import or export the layer data using the Fireworks method.
There is no expectation that we will ever be able to handle Fireworks layer data in PNG files.
We acknowledge that being able to support Fireworks PNG files would be of great benefit to users of Affinity.  If a public definition of the data format becomes available, we will be able to address the issue.
 
Layered TIFF files
There is no such thing as "layered TIFF".  The TIFF standard only handles flattened images as part of the publicly described tags.
TIFF does allow for companies to register additional tags for their own use. Adobe registered two private TIFF tags that enable them to embed layer data in a TIFF.  These tags are an extension and are not part of the central TIFF standard.  These tags are used to embed PSD layer data into a TIFF, in addition to the standard flattened image.
Since Affinity has a PSD importer, we are able to import the layer data from a TIFF if it has these tags.  However, since this is handled by our PSD importer it is subject to the same limitations as importing a standard PSD into Affinity.  We make clear that while we aim to provide the best third party support for PSD, we can never replicate 100% the way Photoshop handles and displays a PSD file.  Photoshop has its own approach to applying alpha/transparency, vector masks and vector strokes, layer effects and gradients.  This means that while we can offer importing of editable elements of a PSD file, the result will not be a one-to-one pixel reproduction of what you see in Photoshop.
We have registered our own TIFF tags for embedding Affinity layer data in a TIFF, in similar fashion to PSD layer data. This is intended for use with DAMs that use TIFF as their interchange format.  When saving a TIFF file, if your document has multiple layers you will be given the option of including Affinity layer data.  This will preserve the editable elements of a multi-layer document.  This obviously comes at a cost of increased file size.  Our TIFF tags will use our proprietary data format and as such can only be used by Affinity applications.
At this time we have no plans to save TIFF files with the PSD format layer data.  PSD layer data held in a TIFF file will be imported and converted to the Affinity format.

Improvements to Node tool will be done at some point.

I'd be real happy when Affinity doesn't have to make their software in order to accommodate PS users and all their needs. I say just make your software, stand by it and let the PS users of world move over to us! These chains will be broken! 

It's on the roadmap already.

Since this subject comes up often I am writing a definitive statement.
Fireworks (layered) PNG files
There is no such thing as "layered PNG".  The PNG standard does not define a way to store layers, and only deals with flattened images.
Fireworks saves out additional layer data to PNG files in a proprietary format using a private tag. A definition for this proprietary data has never been made public.  A PNG saved by Fireworks can still be used as a flattened image by any application that can handle PNG files.  These applications will handle the standard data and ignore the proprietary Fireworks data.
Affinity handles standard PNG files.  But, it cannot import or export the layer data using the Fireworks method.
There is no expectation that we will ever be able to handle Fireworks layer data in PNG files.
We acknowledge that being able to support Fireworks PNG files would be of great benefit to users of Affinity.  If a public definition of the data format becomes available, we will be able to address the issue.
 
Layered TIFF files
There is no such thing as "layered TIFF".  The TIFF standard only handles flattened images as part of the publicly described tags.
TIFF does allow for companies to register additional tags for their own use. Adobe registered two private TIFF tags that enable them to embed layer data in a TIFF.  These tags are an extension and are not part of the central TIFF standard.  These tags are used to embed PSD layer data into a TIFF, in addition to the standard flattened image.
Since Affinity has a PSD importer, we are able to import the layer data from a TIFF if it has these tags.  However, since this is handled by our PSD importer it is subject to the same limitations as importing a standard PSD into Affinity.  We make clear that while we aim to provide the best third party support for PSD, we can never replicate 100% the way Photoshop handles and displays a PSD file.  Photoshop has its own approach to applying alpha/transparency, vector masks and vector strokes, layer effects and gradients.  This means that while we can offer importing of editable elements of a PSD file, the result will not be a one-to-one pixel reproduction of what you see in Photoshop.
We have registered our own TIFF tags for embedding Affinity layer data in a TIFF, in similar fashion to PSD layer data. This is intended for use with DAMs that use TIFF as their interchange format.  When saving a TIFF file, if your document has multiple layers you will be given the option of including Affinity layer data.  This will preserve the editable elements of a multi-layer document.  This obviously comes at a cost of increased file size.  Our TIFF tags will use our proprietary data format and as such can only be used by Affinity applications.
At this time we have no plans to save TIFF files with the PSD format layer data.  PSD layer data held in a TIFF file will be imported and converted to the Affinity format.

@dariobros
 
We've stated it many times before - there is no such thing as "layered PNG" - it is proprietary data inserted into a standard PNG that Fireworks uses. Since that data has no public documentation it is next to impossible to open a PNG with Fireworks data and retrieve the layers (for any app other than Fireworks).  Also, since the Fireworks PNG format was not created by Adobe, we can't use our knowledge of Adobe files formats as a starting point to try decode this data.
 
@CartoonMike
 
There is also no such thing as "layered TIFF" - and it is not in the standard.  What is in the standard are two TIFF tags assigned to Adobe which they use to embed PSD layers into a TIFF, but the content of those tags is not explained in the TIFF standard.  TIFF itself only supports flattened images.  A number of apps can read the Adobe tags from a TIFF, but it is subject to the same PSD import limitations that we always talk about.  The support for layered TIFF is only as good as the support for PSD import, which is a moving goal.  Adobe also has its own methods for applying alpha, layer effects, gradients, etc. These all affect how closely a third party app can replicate a PSD in composition.  I can guarantee that no third party app will produce 100% pixel match for Photoshop if they also support layer effects, vector masks, gradients. PSD doesn't contain a rasterised version of layer effects, so a lot of third party apps cannot import those if they rely on using the rasterised version of layers.
 
We have also registered TIFF tags to allow us to embed Affinity layer data into TIFF files.  So, like with PSD, if your exchange file format for use with a DAM is TIFF, then you can optionally preserve your Affinity layers.
 
Of course, our recommendation is that you stay with a proper Affinity file because that will give you the best performance and file size, and use our export options for creating publication formats.

Ability to edit guides in other tools will be coming soon.  When it is done, you'll be able to place a guide on a node when in the Node/Pen tools.

Since this subject comes up often I am writing a definitive statement.
Fireworks (layered) PNG files
There is no such thing as "layered PNG".  The PNG standard does not define a way to store layers, and only deals with flattened images.
Fireworks saves out additional layer data to PNG files in a proprietary format using a private tag. A definition for this proprietary data has never been made public.  A PNG saved by Fireworks can still be used as a flattened image by any application that can handle PNG files.  These applications will handle the standard data and ignore the proprietary Fireworks data.
Affinity handles standard PNG files.  But, it cannot import or export the layer data using the Fireworks method.
There is no expectation that we will ever be able to handle Fireworks layer data in PNG files.
We acknowledge that being able to support Fireworks PNG files would be of great benefit to users of Affinity.  If a public definition of the data format becomes available, we will be able to address the issue.
 
Layered TIFF files
There is no such thing as "layered TIFF".  The TIFF standard only handles flattened images as part of the publicly described tags.
TIFF does allow for companies to register additional tags for their own use. Adobe registered two private TIFF tags that enable them to embed layer data in a TIFF.  These tags are an extension and are not part of the central TIFF standard.  These tags are used to embed PSD layer data into a TIFF, in addition to the standard flattened image.
Since Affinity has a PSD importer, we are able to import the layer data from a TIFF if it has these tags.  However, since this is handled by our PSD importer it is subject to the same limitations as importing a standard PSD into Affinity.  We make clear that while we aim to provide the best third party support for PSD, we can never replicate 100% the way Photoshop handles and displays a PSD file.  Photoshop has its own approach to applying alpha/transparency, vector masks and vector strokes, layer effects and gradients.  This means that while we can offer importing of editable elements of a PSD file, the result will not be a one-to-one pixel reproduction of what you see in Photoshop.
We have registered our own TIFF tags for embedding Affinity layer data in a TIFF, in similar fashion to PSD layer data. This is intended for use with DAMs that use TIFF as their interchange format.  When saving a TIFF file, if your document has multiple layers you will be given the option of including Affinity layer data.  This will preserve the editable elements of a multi-layer document.  This obviously comes at a cost of increased file size.  Our TIFF tags will use our proprietary data format and as such can only be used by Affinity applications.
At this time we have no plans to save TIFF files with the PSD format layer data.  PSD layer data held in a TIFF file will be imported and converted to the Affinity format.

No problem.  ;)
 
The subject keeps getting brought up by people - and most people don't understand that a lot of these "features" are not part of the global standards. I think we should write a final statement somewhere. :)

Since this subject comes up often I am writing a definitive statement.
Fireworks (layered) PNG files
There is no such thing as "layered PNG".  The PNG standard does not define a way to store layers, and only deals with flattened images.
Fireworks saves out additional layer data to PNG files in a proprietary format using a private tag. A definition for this proprietary data has never been made public.  A PNG saved by Fireworks can still be used as a flattened image by any application that can handle PNG files.  These applications will handle the standard data and ignore the proprietary Fireworks data.
Affinity handles standard PNG files.  But, it cannot import or export the layer data using the Fireworks method.
There is no expectation that we will ever be able to handle Fireworks layer data in PNG files.
We acknowledge that being able to support Fireworks PNG files would be of great benefit to users of Affinity.  If a public definition of the data format becomes available, we will be able to address the issue.
 
Layered TIFF files
There is no such thing as "layered TIFF".  The TIFF standard only handles flattened images as part of the publicly described tags.
TIFF does allow for companies to register additional tags for their own use. Adobe registered two private TIFF tags that enable them to embed layer data in a TIFF.  These tags are an extension and are not part of the central TIFF standard.  These tags are used to embed PSD layer data into a TIFF, in addition to the standard flattened image.
Since Affinity has a PSD importer, we are able to import the layer data from a TIFF if it has these tags.  However, since this is handled by our PSD importer it is subject to the same limitations as importing a standard PSD into Affinity.  We make clear that while we aim to provide the best third party support for PSD, we can never replicate 100% the way Photoshop handles and displays a PSD file.  Photoshop has its own approach to applying alpha/transparency, vector masks and vector strokes, layer effects and gradients.  This means that while we can offer importing of editable elements of a PSD file, the result will not be a one-to-one pixel reproduction of what you see in Photoshop.
We have registered our own TIFF tags for embedding Affinity layer data in a TIFF, in similar fashion to PSD layer data. This is intended for use with DAMs that use TIFF as their interchange format.  When saving a TIFF file, if your document has multiple layers you will be given the option of including Affinity layer data.  This will preserve the editable elements of a multi-layer document.  This obviously comes at a cost of increased file size.  Our TIFF tags will use our proprietary data format and as such can only be used by Affinity applications.
At this time we have no plans to save TIFF files with the PSD format layer data.  PSD layer data held in a TIFF file will be imported and converted to the Affinity format.

No problem.  ;)
 
The subject keeps getting brought up by people - and most people don't understand that a lot of these "features" are not part of the global standards. I think we should write a final statement somewhere. :)

No problem.  ;)
 
The subject keeps getting brought up by people - and most people don't understand that a lot of these "features" are not part of the global standards. I think we should write a final statement somewhere. :)

@dariobros
 
We've stated it many times before - there is no such thing as "layered PNG" - it is proprietary data inserted into a standard PNG that Fireworks uses. Since that data has no public documentation it is next to impossible to open a PNG with Fireworks data and retrieve the layers (for any app other than Fireworks).  Also, since the Fireworks PNG format was not created by Adobe, we can't use our knowledge of Adobe files formats as a starting point to try decode this data.
 
@CartoonMike
 
There is also no such thing as "layered TIFF" - and it is not in the standard.  What is in the standard are two TIFF tags assigned to Adobe which they use to embed PSD layers into a TIFF, but the content of those tags is not explained in the TIFF standard.  TIFF itself only supports flattened images.  A number of apps can read the Adobe tags from a TIFF, but it is subject to the same PSD import limitations that we always talk about.  The support for layered TIFF is only as good as the support for PSD import, which is a moving goal.  Adobe also has its own methods for applying alpha, layer effects, gradients, etc. These all affect how closely a third party app can replicate a PSD in composition.  I can guarantee that no third party app will produce 100% pixel match for Photoshop if they also support layer effects, vector masks, gradients. PSD doesn't contain a rasterised version of layer effects, so a lot of third party apps cannot import those if they rely on using the rasterised version of layers.
 
We have also registered TIFF tags to allow us to embed Affinity layer data into TIFF files.  So, like with PSD, if your exchange file format for use with a DAM is TIFF, then you can optionally preserve your Affinity layers.
 
Of course, our recommendation is that you stay with a proper Affinity file because that will give you the best performance and file size, and use our export options for creating publication formats.

Just to set straight what was said above: Nobody has access to the sales information apart from Apple themselves - they will never pass the information to any developer, no matter who they are. We have absolutely no way to verify that you have bought a copy of Affinity Designer/Photo apart from looking at the embedded receipt in your application on your Mac. If we do that, we could theoretically unlock a Windows license... but if we did that, it only works one way - if you buy the Windows version we can't give people a free download from the App Store - there is no facility for this.
 
[Edited to clarify: The receipt in your Mac App Store application simply validates that you have indeed purchased it, but it will not reveal any details that could be used to identify you]
 
You can argue as much as you like about whether the product is worth $50 or not (we think it's worth more than that, that's why we set it at a very reasonable $50 as we thought we were being really fair and people would be happy). Other programs may offer less, more or just generally different things, some are single-platform, some are multi-platform, but none of them offers the same level of software for the money in my opinion.
 
I think we've been pretty clear about the fact that it's not technically possible to offer anything apart from a one-way licensing scheme that would require everyone to always buy it on the Mac App Store first and then we give them a free Windows-download. That's not particularly realistic or fair, so we're just saying 'Buy it on each OS you want to use it on'. Not too much underhanded or deceptive behaviour going on in my opinion? :S
 
If the future brings a Mac version that isn't sold solely through the App Store then it's valid to revisit this discussion, but that isn't on our roadmap right now, at least not that I'm aware of...
 
Thanks,
Matt