Both share overlapping features, which causes considerable problems:
Having to maintain two versions
Code duplication / complexity
UX complexity and potential confusion
Different space requirements between the versions may require different UI solutions, which may lead to confusing UX.
With these issues in mind, it is important to ask whether having 2 versions is viable. If not, can we combine them into one? If so, how?
Why did we have two versions anyway?
The Inspector serves one essential purpose: Allowing users to try out different resources without losing context.
The full-page view serves two purposes:
providing lots of screen space for space-hungry features, such as recommendations. (MUST HAVE)
making individual OERs addressable (thus shareable) using a permanent URL. (NICE TO HAVE)
Proposal
Rather than having two versions, let's improve the inspector so that it allows the same essential functionality as the full-page view. Then we can get rid of the full-page view.
Showing recommendations is clearly a must, so let's add a sidebar to the inspector (as we had before for notes - but this time, let's use tabs like we had in the fullpage view). Let's also make sure that we use the screen space optimally. I.e.:
Keep the sidebar as small (narrow) as possible
Don't waste space on non-essential features
On narrow screens, if necessary, consider overlapping the navigation drawer rather than overlapping the right screen edge
With regard to shareable URLs, let's replace /resource/123 with /search?q=123. This way, we get shareable URLs without introducing additional complexity. Similar to the wikidata website, where the search input field accepts keywords as well as ids. When the user enters a valid id into the search field, they get a single card as a result. By the same token, if someone sends you a URL like /search?q=123 you get a single card, just like you would if you had searched for it yourself.
Alternative solutions for URL sharing
There are different ways to ensure that the user can get a shareable URL. E.g.
adding a share button which gives the user a copyable absolute URL, similar to stackoverflow.com.
adding a simple "permalink to this resource" link similar to xkcd.com
making sure that the browser's address bar shows a shareable URL (preferred option)
Goals
[x] Add sidebar to inspector (defaulting to feedback tab, including recommendations tab)
[x] Ensure that /search?q=123 produces a single card containing the OER with the id 123
[x] Ensure that /search?q=123&i=123 produces the card and open inspector containing the OER with the id 123
Problem
Inspector and full-page view are similar.
Both share overlapping features, which causes considerable problems:
With these issues in mind, it is important to ask whether having 2 versions is viable. If not, can we combine them into one? If so, how?
Why did we have two versions anyway?
The Inspector serves one essential purpose: Allowing users to try out different resources without losing context.
The full-page view serves two purposes:
Proposal
Rather than having two versions, let's improve the inspector so that it allows the same essential functionality as the full-page view. Then we can get rid of the full-page view.
Showing recommendations is clearly a must, so let's add a sidebar to the inspector (as we had before for notes - but this time, let's use tabs like we had in the fullpage view). Let's also make sure that we use the screen space optimally. I.e.:
With regard to shareable URLs, let's replace
/resource/123with/search?q=123. This way, we get shareable URLs without introducing additional complexity. Similar to the wikidata website, where the search input field accepts keywords as well as ids. When the user enters a valid id into the search field, they get a single card as a result. By the same token, if someone sends you a URL like/search?q=123you get a single card, just like you would if you had searched for it yourself.Alternative solutions for URL sharing
There are different ways to ensure that the user can get a shareable URL. E.g.
Goals
/search?q=123produces a single card containing the OER with the id 123/search?q=123&i=123produces the card and open inspector containing the OER with the id 123