Wanderus is an app, that allows a user to not only explore the various "experiences" that one's friends have had, but it allows one to also share experiences. In an era focussed on sharing experiences, Wanderus provides a streamlined social platform to do so. It combines the search functionality that many other social apps are used for in younger generations, while maintaining a social componenet.

Wanderus focusses not just on its functionality, but also its clean aesthetics, with intuitive interface.

Currently I am in the process of prototyping it. So stay tuned!


Create a new social media platform that remains familiar as a social app, but yet also has the added functionality as a search app - additionally, maintain brain aesthetic, that caters to a generation focussed on aesthetics.

This proved to be a difficult task for it requires the backend data to be structured radically different from other apps. Not only does it need to contain "posts" unique to each user, but it also needs to have "posts" that refer specific to the location/"experience" regardless of user. So theoretically, the structure of the app has been conceptualized to have both distinct pieces of data, with individual's "experiences" acting as a connection to those specific "experiences." Additionally, the locatin/"experiences" can be accessed remotely through the search functionality.


Utilize existing and familiar UX frameworks seen through out social media platforms to make an intuitive layout, but still modernize by injecting new and streamlined styling of familiar UI.

*I do not own the photos used in this mockup. They are used for purely for presentation. They are owned by Steven Fingar.

The login and registration screen is straight forward. I wanted it to be simple.

The next screen is that of the home screen and what happens when you long click on the post. Again the goal here is to make things intuitive and not too complicated. So given that this works as a social platform, the typical interface is used to evoke a sense of familiarity.

The actual post screen is an overlay, with the images on top being parallax. As you scroll down, you have an "X" appear to allow for quick access back to the original screen.

This also served as an interesting back end conflict - the way that it is structured is that users can have individual posts, but also have locations they have been to. The posts serve as a way to share a specific experience, whereas the overall location is help separate, related to all instances that that user has visited, but also all the other posts from other users. That is why there are different tabs to structure the different pieces of information in a more coherent manner.

In terms of design of the post screen, slight gradients were used to really reinforce the idea that this is an overlay, rather than a separate screen.

The explore screen is clean and gets to the point. However, again what you see here are photos from individual posts, but they are linked to the location itself. (If that makes sense!) The explore page serves more as a tool for users who seek new places to go to rather than a place to look at specific posts. This really gets at the root of the problem of trying to make a social platform that also serves a function.

The bookmark screen below allow for users to save experiences, either by post (or experience) or by location and then actually categorize them. Users have options to see all of them, or categorize them into collections, or developing just view the experiences that they liked.

he final screens are about the profile. Again, I did not want to deviate too much from the standard profile UI's implemented. So for the profile screen, users can view their experiences as posts (organized by date), in a grid format (organized again by date), collections (which are curated by themselves), or via the map (which provides a way to look specifically by location).