CraigB

First: I'm not asking for help or feedback.
I'm only reporting that I see the same delay when modifying text styles in Publisher v.2. It's usually a 5-6 second spinning beach ball that freezes Publisher & CPU usage for Publisher spikes >100% for a single CPU.
I've been running Publisher since it was originally released and this is a new behaviour that was not present in v.1.
I'm running a Mac Studio Ultra (20/64/32) with 128GB Ram on the most recent version of MacOS.

First: I'm not asking for help or feedback.
I'm only reporting that I see the same delay when modifying text styles in Publisher v.2. It's usually a 5-6 second spinning beach ball that freezes Publisher & CPU usage for Publisher spikes >100% for a single CPU.
I've been running Publisher since it was originally released and this is a new behaviour that was not present in v.1.
I'm running a Mac Studio Ultra (20/64/32) with 128GB Ram on the most recent version of MacOS.

Title says it all. Google PageSpeed is recommending the use of these formats, but AP doesn't support any of them. Please, if possible, do.

@Josegt80 and all readers of this thead
There's no technical problems with ARM, there is simply a lot of functionality, tools and UI to write for Publisher iPad and some back end work in relation to managing large documents with many linked or embedded images. Progress is good and nothing should be insoluble.
It was disappointing to many here that we did not manage to have a 2020 release for Publisher on iPad, but I will leave it to the company leaders to make the announcements of what is happening next.
Also please do not worry about your use of English, feel free to post in your native language if you prefer. [Además, no se preocupe por el uso del inglés, siéntase libre de publicar en su idioma nativo si lo prefiere.]

I'm resurrecting this apparently zombie thread b/c I can not for the life of me figure out how to automatically flow text from spread to spread.
I can get text to flow between text frames on facing pages. But if I have 100 pages of content I have to link each spread together (previous recto frame to following verso text frame). It looks like @Arun Sarkar figured out how to do it automatically but his video is gone.
I've tried every combination of CMD, ALT, and SHIFT I can think of.
I'm attaching a video of how this is done in InDesign in case I'm not explaining myself.
Does anyone know how to do this? I just can't imagine doing this every time I produce a book!
reflow.mp4

I can’t wait for the day when I can retire my MBP...

It is in german, but maybe this can help you.
 
https://www.youtube.com/watch?v=i9Mo1OTD8_M

-

First: Publisher is not on my purchase list at the moment. But, it would definitely be if...
IDML Import:
I have several years worth of Indesign files (stored as IDML) that I need to be able to repurpose: starting a new book from a previously completed one (with the basic styles in place) is a key time-saver and I have clients ask for revisions to old work on a regular basis... So, import of IDML files is the first update. It makes no sense to throw all my babies out with the InDesign bathwater.
Ported to iPadOS:
And now with the release of iPadOS the iPad supports a mouse: which for me is a sea change that will allow the iPad to replace my MacBook when traveling. IF Publisher (like the other Affinity apps) is also ported to iOS (iPadOS) that would be the clincher and I'd be in for both desktop and mobile apps.
With both of those complete I could finally delete the very last Adobe app from my workflow.

I've read all the apologists about a 'maybe later' IDML import. Unfortunately I (and a couple of other book designers I spoke to) don't want to keep 2 tools around for publishing: it's inefficient. And, for us, the single missing feature in Publisher is an import feature for documents created in the software against which Serif is trying to compete (and against which they actively market with their 'no subscription' mantra).
Serif know who their competitors are. For us to accept that they failed to position themselves as a viable upgrade is silly. Few professional designers can afford to make a wholesale change to their workflow without the ability to reuse and update old projects.
To head things off at the pass: I did attempt to import a few PDFs but the imports were quirky at best - and unusable in many instances. Orphaned lines of text within paragraphs, odd page sizes, unlinked text frames...basically impractical for anything beyond a flyer or poster. And doing a copy/paste from INDD is fraught with possible problems - such as the day INDD stops working with MacOS (and that day is coming).
I completed 5 book projects since Affinity released Publisher and could not, in good conscience, produce any of them in a software that may not make it into widespread production. Affinity must set Publisher up to directly compete with INDD and part of that is the ability to import--and create--interchange formats. 
I updated the beta again today in hopes the IDML import feature would have been implemented since the last time I looked. After a test I ultimately deleted the app.
I'll look at it again when Serif announces IDML import functionality (with a comparable interchange export functionality). Hopefully CS6 won't stop working with a future Mac update or I'll be going back to Quark (who added IDML import late last year). If I incur the significant one-time cost to move to Quark I will have little reason to consider Affinity Publisher for a very, very long time.

I can't believe the number of posts requesting Import/Export of ID files. They obviously know this is an important feature for us. They acknowledge that it is being worked on and even gave us a pretty positive response in terms of when we can expect to see the import part of it. I am scratching my head at the number of people acting disappointed... If InDesign is a critical part of your daily work and you require these very specific capabilities this product may not be a smart move for you to consider as it is in the beta phase of development.
The bottom line is you are no worse off today than you were prior to this beta being released. Keep paying Adobe for now... I'm pretty sure they will still take your subscription money.
I am finding the beta amazing. I have not done any print testing as yet. If this program can print what I layout as I expect it to be printed I am all done with Adobe. The only reason I didn't switch from InDesign is because of printing issues. InDesign is an amazing and complicated program. It took many years to get to the level it is at. Let us enjoy the beta journey instead of coming up with unrealistic demands of what it must do for us today. If you require InDesign accept it... That doesn't mean you can't enjoy the process of getting a replacement in the future.
I am so grateful for these products as they truly allow me to have solid well-designed software at great prices. Adobe wants me to make a car payment sized bill every month. I do simple work that requires software that can handle what I throw at it. Serif has been a true gift for me. Adobe can kiss my Butt...
I am finding it amazing... Keep up the great work guys.

I am left wondering if the same people who are criticizing Publisher for no InDesign import/export and Quark import/export will also be on the Adobe and Quark forums criticizing them for no Publisher import/export? For me, this suite of products is the first real alternative to the Creative Cloud solution and at a fraction of the price, I will find ways of working around any shortcomings that may present themselves.
I've seen a lot of very negative comments in these forums, which IMHO are a tad unwarranted. It is an early BETA after all.
My congrats to the Affinity team on what promises to be a great alternative for professional designers and web developers.

Many, many thanks.  Also sounds like importing PDF works reasonably–very well..  However, I'll give the batch converter a trial tomorrow.

I agree with Fixx. I’ve done contract work (book design) where the final product was an InDesign file but that is (for me) a very edge case.
I do, however, have an archive of completed projects that (every so often) I’m asked to update for a client and I really (REALLY!!!) don’t want to have to keep a copy of InDesign on my system. I would like to make a clean break with Adobe and, at this point, InDesign is the holdout. 
That said, I don’t expect the migration to a new desktop layout application to happen overnight. I remember a long and strenuous transition from Quark to InDesign almost 20 years ago that still makes my left eye twitch.
IF Publisher turns out to be viable I can create IDML versions of those projects for which I have not already done so. (My normal workflow is to create an IDML from the final INDD file when a project is complete so I can open files on older versions of InDesign or Quark in a pinch.)
Importing INDD files into Publisher is not as important to me as importing (and possibly exporting) IDML files for maximum forward compatibility.
It would be great if the IDML import successfully imported the character, paragraph, and object styles.
 

Most customers do not want InDesign source files, and most designers do not want to hand them over (unless compensated with $$$).
If you customer insists to have InDesign files, you better use InDesign for the job (I assume that is important customer).
If customer wants to build a work flow where it is possible to use Publisher, price is no problem and customer can purchase it.

I still have CS6 at hand and use it when needed. It is a good backup. But most of my work I do with Affintiy. And am happy with it.
d.

Personally I find Indesign pretty stable, though I stopped upgrading at CS6. I wonder if the expectations of APub are getting too high. I'm sure it will have some amazing new features but there will be lots missing which ID users have taken for granted over the years. Hopefully it will be the start of a long road though I suspect it will be pretty buggy for a while, like most new software.

Yes. I'm replying to my own post! I'm so happy to attach a screenshot of my Adobe Prison Release email. I pulled out my CS6 and installed InDesign to get me through until Publisher is available...
 
No longer will I pay Adobe $55/month. Thanks Serif!
 
Looking forward to the Publisher beta this summer!

Yes. I'm replying to my own post! I'm so happy to attach a screenshot of my Adobe Prison Release email. I pulled out my CS6 and installed InDesign to get me through until Publisher is available...
 
No longer will I pay Adobe $55/month. Thanks Serif!
 
Looking forward to the Publisher beta this summer!

Yes. I'm replying to my own post! I'm so happy to attach a screenshot of my Adobe Prison Release email. I pulled out my CS6 and installed InDesign to get me through until Publisher is available...
 
No longer will I pay Adobe $55/month. Thanks Serif!
 
Looking forward to the Publisher beta this summer!

Yes. I'm replying to my own post! I'm so happy to attach a screenshot of my Adobe Prison Release email. I pulled out my CS6 and installed InDesign to get me through until Publisher is available...
 
No longer will I pay Adobe $55/month. Thanks Serif!
 
Looking forward to the Publisher beta this summer!

Actually, "Balance Ragged Lines" is not supposed to be used on body text. Balancing and hyphenation are taken care of by the paragraph composer – by default that's Adobe's excellent "Multi-Line Composer", which already takes the effect of hyphenation and composition decisions over the entire paragraph into account, not just the current line. So you don't need to activate any other options to get nice and balanced body text.
 
"Balance Ragged Lines" is intended to be used with small centered blocks of text like pull quotes, multi-line headlines and so on. For instance, you can apply it to your subhead paragraph style so that those two lines of text are always evenly divided between the two lines and you don't have to manually add forced returns for everything to look balanced.
 
If you apply "Balance Ragged Lines" to regular body text however, it will actually usually make the result significantly worse, and it is sure to drive anybody mad who has to do copy fitting with your body copy style.
 
If you look at your example, the only thing that has really improved on the right is that InDesign has balanced all lines so that the last line of the paragraph is filled completely, making tradeoffs in all other lines in order to meet that goal. Also keep in mind that placeholder copy won't always give you the best impression of these things since the hyphenation is not representative when using pseudo-latin.
 
EDIT: There is an article on InDesign Secrets that goes into detail.

I've been designing and publishing books and magazines for almost 40 years. I remember learning to use Aldus PageMaker on the Mac II oh those many years ago and over the years I've purchased tens of thousands of dollars of Adobe software and been harnessed to the annoying subscription model for not-quite 3 years. Having stuck with Adobe for an awfully long (and expensive) time I grate my teeth every year when my CC subscription comes up for renewal. And one of the primary reasons I haven't explored other options was InDesign. (I hate Quark...)

I learned of Affinity software today through a post about the Publisher preview on YouTube. Combined with Photo and Designer, I can finally see an end to my Adobe sentence.
 
I downloaded the trials for Photo and Designer and am so impressed I'll learn new workflows over the next two months so I can cancel my CC subscription before the March 2 renewal.
 
I have a break between publishing projects until mid-summer so my fingers are crossed Affinity Publisher will be in beta by then.