Order of blocks on Mobile, should be consistent with Desktop

WHAT IS THE REQUEST

Some things do not appear at all in the app. So far I’m noticing that blocks that are stacked side by side do not show up in the app. For example if I link to objects or reference them with @, if I try to arrange them side by side on the desktop, only some of them show up on the app.

CURRENT BEHAVIOR

Create previews and arrange them side by side by clicking and dragging on the desktop app.

Check the same note in the ios app and you’ll notice it doesn’t show up. It may be because i’m on iphone 12 mini. This would be easy to test out using the xcode mobile simulators

Desktop:

VS.

Mobile:


The behavior is odd. I’d expect the blocks to show up in order right to left, then on the row below, right to left and so on.

THE DESIRED BEHAVIOR

I expect things to look more or less the same

SYSTEM INFORMATION

  • OS:
    ios 16
  • Device:
    iphone 12 mini
  • Anytype Version:
    latest

Could you make some test objects and show print screens of both desktop and iOS?

I think by default all blocks are shown underneath each other, going from left to right, then top to bottom.

I’m trying - it’s not syncing - also another bug - just randomly doesn’t sync. It sometimes takes upwards of a minute to sync - very frustrating when you just want to open the app to make areally quick note.

desktop:

mobile:

Completely removing them and adding them back looks to have helped - still the behavior is odd. I’d expect the blocks to show up in order right to left, then on the row below, right to left and so on.

1 Like

This report has been added to our issue tracker and received by the Development Team.

1 Like

Product team believes supporting multiple columns on mobile screen would be too small, so it’s unlikely we’ll implement this.

Yes the idea was not to have them display side by side but rather, to have them display at all. On mobile, these preview cards that are displayed will randomly not display correctly. This should have been a bug report instead of a feature request

1 Like

I see now. It wasn’t super evident what you meant. I’ve clarified the title and will raise the issue again

1 Like