pachermann

Oh yes please!
My clients want zepplin.io to use.

Click here to download the latest beta
 
Status: Public Beta
Purpose: Stability
Requirements: None
 
As this is a beta release, it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that you may be adversely affected by the application failing. In addition it is worth noting that files created in Affinity 1.5 cannot be opened in 1.4, which means files created with the Windows beta cannot be opened in the Mac AppStore version of Designer, instead you will need the latest macOS beta.
 
We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post here and we'll get back to you as soon as we can. Thanks once again for your continued feedback.   If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum.  
Fixes
Fixed crash when pressing ALT+Spacebar on a floating window Fixed crash using Wacom Bamboo on external display (thanks federix) Fixed middle mouse button panning becoming stuck Fixed PDF import of default widths for Japanese fonts Fixed printers marks smaller borders when bleeds are unequal Added publisher details to Add/Remove Programs Added keyboard support to text styles combobox on the context toolbar Fixed crash when exporting to an SMB share from Export Persona Fixed PDF export failing when adding negative value to Phase for a dashed stroke Fixed embedded documents incorrectly displaying their path when they are edited Fixed 'PDF Information' font changes Fixed crash when making no selection with the 'Show selection in layer panel' option enabled Added document loading message Fixed being able to edit a registration colour by double clicking Fixed crash when clicking on swatch panel after editing a swatch Fixed swatches saved with non-default Opacity/Noise values not being applied to objects correctly Added reporting of warnings when loading PSD files Fixed loading of PSD files with noise gradients (but will just ignore the noise gradients as we can't reproduce them) Fixed measuring between siblings inside groups and containers (can also measure immediate children of a container, and between the selected object and it's ancestors) Fixed preview of masks in Layers panel Fixed Customise Toolbar context menu being available during customisation Fixed Asset panel category changing when the panel is docked/undocked Fixed Character panel not disabling controls when no document is available 

I have a little tip for you to optimize your SVG filesize, it has nothing to do with the tool.
 
personally i think afinity is clean and slick for XML.
 
your svg is that big because your vector works document is technically a bit complicated built for a SVG.
 
SVG is a very old XML standard that should be optimized for Browsers and UIs and afinity exports perfect XML depending on the style the vector has been built.
 
The stroke for example has to be a closed path object, with outlines and so on.
mirrored objects and stroke effects are very complicated to be displayed vs closed path objects.
 
- make closed vector forms
- be sure only group objects if necessary
- export text as path only if the target media does not have the font
- never use bitmap part inside of SVG
 
i have here an example of a little closed path and a stroke to see the difference.
 
The stroke has crazy values to simulate these complex strokes.
 
I had to zoom out in order to show you how many code is needed for that stroke effect vs closed path objects in SVG (XML)
 
left is a closed path object (only scribbled for example) right is a stroke with effects  

 
the first object is very short and efficient XML code id="closed path" and the second one is HUGE XML stroke interpolation  

 
 
 
I hope it helps to optimize SVG files :)
 
best,
pascal

I have a little tip for you to optimize your SVG filesize, it has nothing to do with the tool.
 
personally i think afinity is clean and slick for XML.
 
your svg is that big because your vector works document is technically a bit complicated built for a SVG.
 
SVG is a very old XML standard that should be optimized for Browsers and UIs and afinity exports perfect XML depending on the style the vector has been built.
 
The stroke for example has to be a closed path object, with outlines and so on.
mirrored objects and stroke effects are very complicated to be displayed vs closed path objects.
 
- make closed vector forms
- be sure only group objects if necessary
- export text as path only if the target media does not have the font
- never use bitmap part inside of SVG
 
i have here an example of a little closed path and a stroke to see the difference.
 
The stroke has crazy values to simulate these complex strokes.
 
I had to zoom out in order to show you how many code is needed for that stroke effect vs closed path objects in SVG (XML)
 
left is a closed path object (only scribbled for example) right is a stroke with effects  

 
the first object is very short and efficient XML code id="closed path" and the second one is HUGE XML stroke interpolation  

 
 
 
I hope it helps to optimize SVG files :)
 
best,
pascal