a use-case we've encountered several times now is:
A Lens should be published both as a sponsored lens and as a community lens.
The reason for this is that it needs to be sponsored so we can put ads behind it and we want it to be a community lens so users can find it via the search function in the community section and so the lens will also benefit from this natural way of gaining user attention.
The current workflow is:
1) Upload the Lens and select Sponsored Lens + do all necessary publishing steps
2) Upload the Lens and select Community Lens + do all necessary publishing steps
That itself is not too much effort.
The problem is, that updating the lens becomes a bit of a mess since you have to do both steps every time.
The danger in this approach is that one of the two steps might be forgotten and you'd end up with one of the lenses not being updated.
Our suggestion is:
Have an initial step where the "build" of the lens is uploaded and then the build can be selected to be used as sponsored or community lens.
And after the build is processed enable the user to select what to do with it.
Publish as new lens or update existing lens.
If update existing lens is selected the user would be able to select both the sponsored lens and the community lens on the same screen.
This should make this process less error prone and it would satisfy our use-case.
An alternative solution could also be that all sponsored lenses automatically be submitted as community lenses as well.
And when updating the sponsored lens, the community lens would also be updated since it would be the same lens in terms of the build.
That would also make it unnecessary to do two submissions or have the before mentioned "build upload system".
Thanks for considering this!
Please sign in to leave a comment.