Views consistency across devices for inline sets

WHAT DO YOU RECOMMEND

An inline set in a page should provide the same views on mobile. Actually the inline set displayed on mobile link to the master set, not the one customized for a particular embedding in a specific page

HOW COULD IT BE DONE

Consistency across devices.

REAL WORLD USE CASES

The inline task set on my dashboard shows only tasks with specific relations because I don’t need to see all my task set content in the same time.

RECOMMENDED ALTERNATIVES

I duplicate the same views on the master set

Hi @Elias. We are going to fix it via real inline sets capabilities on mobile devices. For now it leads to the source set for the sake of simplicity because inline sets is already complicated concept.

8 Likes

Ok, thanks for your feedback.

1 Like

@ignatovv is there an ETA for this? It’s hard to use sets and collections on mobile without this

Hi @raph, this update in the product backlog at the moment. Could not give exact time of fix, but it will come in par with updates for inline sets. Roughly Q4 23 - Q1 24

5 Likes

WHAT DO YOU RECOMMEND

Currently, you can create an inline set on desktop and use it to filter a set. This is useful, because you can show a subset of the set on a page, according to some filters based on its relations. However, if you then navigate to this set on your android device, you are shown the ‘original set’ without any of the filters. This is not ideal.

At the moment, sets are superior than collections for many use cases in this context becauseː

  1. You can edit relations and have them be propagated still.
  2. It is still possible to display multiple types, by having a set of the type object types and filtered for the object types you want. Honestly, because collections require so much manual work, this makes sets like this just ‘collections but actually useful’ for basically all my own use-cases. (Mine aren’t the be all end all, of course.)

The only other way around this is to create a set for every page - this is maybe ideal for some use cases, but for my own this would just create annoying clutter - and more work, it for sure takes more time than just having a templated inline set. I do wonder which way would be more performant, though…

HOW COULD IT BE DONE

Basically you tap on the set and it shows you the set with the correct filtering as expected given the inline set. If you then want to go to the ‘original set’ which presumably represents the original ‘unfiltered’ set in the sense of it being the superset of the subset, just give a context menu or icon to do so. (Of course, that set itself may have been filtered if you use the object-type filter to show multiple object types in the set, but it’s ‘unfiltered’ in the sense that that is the set of things you want.)

REAL WORLD USE CASES

Pretty much everywhere and any use case I can imagine for inline sets. My practical example is this howeverː I’m currently doing a trip planner and some things for the trips are not the same type, so I need sets to show multiple types. Additionally to that, I like to filter that set by area, so I can pull up relevant stuff quickly; for this I am using inline sets. This works fine on desktop, but it just doesn’t work on Android.

RECOMMENDED ALTERNATIVES

As I said, you can just create an individual set for each page. This creates a lot of work and clutter - the former being the main objection.

ADDITIONAL CONTEXT

There is a previous FR for this feature for desktop. People had opened bug reports, but I see no FR for this feature on android indepedent of the original (now closed) desktop FR.

Thanks for your time, and for the appǃ

Ah - I didn’t find this FR when I wrote the above. Thanks for merging into this one - good to know it’s on the radar. :slight_smile:

1 Like