ALx

+1 for editing width directly on the curve!
 
While we are at it, how about a little extension to the pressure panel allowing for inputting math functions /parametric widths? :)

+1 for editing width directly on the curve!
 
While we are at it, how about a little extension to the pressure panel allowing for inputting math functions /parametric widths? :)

Just utilise Layer Effects panel for this? The Effects could be treated as layers and there could be unlimited number of them — something similar to Illustrator's Appearance panel perhaps?
 

Just utilise Layer Effects panel for this? The Effects could be treated as layers and there could be unlimited number of them — something similar to Illustrator's Appearance panel perhaps?
 

I'd say this could be a perfect case for a plugin. However, considering the current roadmap, it's unlikely we will see plugin functionality in AD/AP v1.x. Hopefully in v2.0 because Adobe introduced plugins in Photoshop 2.0 and Affinity can't be worse!  :D

Forgive me my ignorance but how would it be different/better from OS X built in file versioning?

You did :) It's called per-point or variable-width feathering. Affinity folk have approved this feature here but am not sure when it's coming and to which apps?

Allow for the document story to be uploaded to the cloud to be remotely edited in a collaborative environment. 
 
I'd like to see something akin to InDesign-InCopy workflow but much easier/better — without installing additional software and doing it entirely via a web interface.
 
Every now and then a project happens where a copy needs to be edited by either a client or a bigger group of authors/editors/proofreaders. We all know how it looks on average — lots of phone calls or emails with tons of text changes, unbearable Word docs for you to copy/paste the shit throughout the day. Bigger projects can deploy InCopy but it means purchasing additional software and then learning it and your average client won't like this very much (I've been there!).
 
But still it's pretty awesome to be able to just click 'update' after an editor sends you changes via InCopy and watch text and tables magically update. You just focus on the design, yay!
 
I think, with today's technologies, it could be possible to ditch additional software, sync document story to the cloud and build a web interface where clients and editorial team would work on the copy. Having a web interface would take away all the problems associated with software installation (documents could be accessed anywhere, from any device) and be more client-friendly.
 
Does that sound remotely (pun intended) possible?  B)

I honestly don't think this can be patented: https://youtu.be/ejIIvrQk2tw  B)

I honestly don't think this can be patented: https://youtu.be/ejIIvrQk2tw  B)

No, he didn't.
 
Snapping was completely overhauled a while ago to accommodate custom grids and axis.  At that time some features got pushed back (such as gaps and spans) until they work with the new system.  There were other features I had written that needed a lot of tweaking before they could be deemed to meet the required quality.
 
Snapping to text has always needed addressing in a special way - much because we need to find  solution that doesn't become too busy, while still allowing the user to achieve obvious snaps easily.
 
I am looking at snapping right now, and will try improve as much of this as possible for the next Beta.

I honestly don't think this can be patented: https://youtu.be/ejIIvrQk2tw  B)

Exactly! A-to-B paths have always been a strange limitation to me, especially when drawing maps where you want to join multiple paths to a single point. Interestingly, AI's Mesh Tool is something of an in between of the two methods.
 
Matt, I hope they won't patent it. (And can they? Isn't it essentially a 2D representation of multiple lines connecting to a node in all 3D software?) Open source is the future!  :)

Publisher documents should have the notion of Sections
 
InDesign documents have the notion of Chapters, if one is working on a book type document. Non-book documents do not have a section-level grouping of content. Yes, there are "sections" that one can create using the "Number & Section Options" in the Pages panel but these "sections" are not really first class citizens in the document. Rather they're more like a meta citizen.
 
In particular, there is no way to use the "section marker" in numbered lists.
 
Publisher should implement Sections in such a way that sections can be referenced in a variety of ways, and in particular section numbers should be available in numbered lists.
 

Exactly! A-to-B paths have always been a strange limitation to me, especially when drawing maps where you want to join multiple paths to a single point. Interestingly, AI's Mesh Tool is something of an in between of the two methods.
 
Matt, I hope they won't patent it. (And can they? Isn't it essentially a 2D representation of multiple lines connecting to a node in all 3D software?) Open source is the future!  :)

I have to disagree whole heartedly with using a scripting language for plugins. Scripting languages should be used for what they were designed for: scripting. The way I see it a plugin adds a new feature ex. a new filter on an image and needs to implemented in pre-compiled languages as it will be interacting with vital program data. A script activates functions in the application the same way a user would by clicking something in the GUI thus allowing for automation of repetitive tasks, These are two very different things and should be treated as such IMO

We are going to make a professional Affinity DAM application - stay tuned in 2016 for more information ;)
 
Thanks,
 
Andy.

I think this is an important area anywhere you use text. Even Photo can benefit from paragraph/character styles as proved by years and years of pushing Adobe to improve this area in Photoshop. :)

Interesting idea! I've mocked up a quick example based on my earlier navigation concept I did for a client. Not sure how you'd show adjustment layers but overall it would definitely ease traversing through complex layer trees.
 

Dear Affinity Team,
 
First, let me congratulate you for picking up the Apple Design Award! Well deserved!
 
While I know you're at the beginning of a long and winding development path and it will be a while when all of your software receives all planned features and more, I was wondering about the bigger picture. Can you excite us with your long-term vision for Affinity Suite?
 
In general, do you see it as a standalone easy to use software for everyone or maybe more as an open, powerful architecture that could be extended and adapted to various specialised environments and industries? I think it's interesting from the technological point of view where new exciting tools seem to move towards automation, scripting, connectivity, server-side deployment etc... Will we be using Affinity Designer of the future to produce an elaborate infographic poster based on real-time data feed or Publisher to instantly create a book based on user input while making an order on the Internet? All that while waving our hands mid-air? Yes? No? :)
 
Thanks and keep up the good work!
 
Alex

+1
 
I currently use Motionize plugin by Scott Ash for AI. It works but a big limitation is it's inability to export compound shapes and you need to be really careful with the layer structure. Everything is nicely explained on his site.

+1 for editing width directly on the curve!
 
While we are at it, how about a little extension to the pressure panel allowing for inputting math functions /parametric widths? :)

+1
 
I currently use Motionize plugin by Scott Ash for AI. It works but a big limitation is it's inability to export compound shapes and you need to be really careful with the layer structure. Everything is nicely explained on his site.

An absolute must-have!

Regarding naming, there's a bit of inconsistency to me with names Designer, Photo and Publisher. Shouldn't it be Photographer? I realise it's too long, so maybe Retoucher? This way you avoid the problem with abbreviations, too — AD, AR, AP. You welcome  :)