Comparison with Panelizer?

Yep, I use Panelizer a lot.

Panelizer is great when you want one way of viewing content. Of course there are different view modes in Panelizer, but still all users see the output in the same way.

This module let users drag n' drop their own way of seeing things. Think about the dashboard on d.o. Everyone has the same blocks, but you can dnd your own order of blocks and hide blocks from display. Exactly this is what the module does. The administrator provide sane defaults, by creating a normal panel page. The user can override the 'sane' defaults with his/her own preference.

I use it in a issue tracker. Every type of user finds different stuff important. The project lead wants to see who is working on the issue, and when it is planned, the dev wants to see all attached files, screenshots and descriptions.

Note!
I didn't test it with Panelizer. It might or might not work... but it seems overkill to me, to use this with Panelizer. Panelizer provides defaults per view mode of a entity bundle (node type). You can override that per instance (per node). That makes that you have a lot to override as a user. Looks like a nightmare to me :)

Hmm yeah,
When you post it like this... it still seems to me that Panelizer and this module can be compared. But they cannot. They both have a different use case.

Users can change the way they see the page. (it does not have to be their content i.e. ownership of the content). So they only change how he or she sees the page. Just think about the dashboard module :) it has exactly the same functionality ... it is only based on panels.

It is even more specific... it allows users to change the way they see a display.

On a normal panel that is:
object -> selection based on context -> variant/display

With Panelizer that is:
Entity -> view mode (defaults) -> instance (override per instance) -> display

All displays can be overriden. That makes it pretty useless in combination with Panelizer, because there can be a gazzilion different displays (each instance ('node') can have its own display)... My conclusion, it might work, but is unmanageable.

I find it rather difficult to explain on the project page. When I start comparing with (or giving differences to) panelizer, it brings a whole different concept in the mind of a reader. Don't you think that will be too confusing? It simply is not Panelizer and cannot be compared.

Made a remark on the project page... let's see if that is clear enough :) Let me know when I can do better.