Eusebius

Hello,
It has been a while since I visited this thread to see the progress on implementing footnotes and endnotes in Affinity Publisher. I'm very happy to hear there is some progress seemingly coming this year. In the meantime — and please don't take this the wrong way — the lack of these features in AP has forced me to use Adobe InDesign even more and given me a new appreciation of what ID can do. Before, it was really clunky and slow, but the latest updates to ID running on Apple Silicone make it a whole new experience that is actually... usable (at least for me.)
I still love the potential of Affinity Publisher (especially running on Apple Silicone) and look forward to the new updates.
Keep up the good work

Hello, again,
We are here at the end of March and I would like to report the situation persists with me. On both our 2019 Mac Pros (an 8-core with 64 GB RAM and Radeon 580x and a 16-core with 384 GB RAM and a Radeon Vega II), the Affinity apps are painfully slow to load up. 
I was under the impression that the latest update fixed that issue, but it doesn’t seem to be the case with me. 
FYI, I’m running the App Store versions of Photo and Designer, and the direct version of Publisher. 
Any ideas?
Thank you 

Welcome, Julein!
Assuming you're using Affinity Publisher, you have to remember it's not like a word-processor. You have to create text frames and then link the frames together so that the program knows you want text to go from one frame to another. For books, this is usually done by creating a Master Page with a full spread. Afterwards, you will create text frames on the left side and right side of the spread. Finally, you will link those text frames together. Now, when you add new pages based on that Master Page, it will automatically flow the text from one frame to the other.
I hope that is helpful. You can also find several videos on YouTube describing this process. 
 

The app has to use iOS 13’s custom font API. Looks like Affinity’s apps haven’t been updated for that yet. 

The app has to use iOS 13’s custom font API. Looks like Affinity’s apps haven’t been updated for that yet. 

Link the text frames on the master pages. Otherwise Publisher doesn't know it's supposed to use both for the same story.

As ever, it was a choice between releasing the product without that feature, or delaying for however long it took to add it. If we waited until footnotes, database merge and IDML import were done, that could easily be another six months. It turns out that a lot of customers can be productive without those features, so we chose to release now. If you aren't one of those customers, that's unfortunate, but you aren't actually worse off today because it was never feasible to have the features ready for today.

Yes, I agree with all those who are requesting implementation of footnotes/endnotes. I'm sure it will require some programming effort to do it right, but it is an absolutely essential feature for serious desktop publishing, which includes books, magazine articles, and academic publications. 

Yes, I agree with all those who are requesting implementation of footnotes/endnotes. I'm sure it will require some programming effort to do it right, but it is an absolutely essential feature for serious desktop publishing, which includes books, magazine articles, and academic publications.