We analysed the top 3 most commonly used social media platforms that all our users reported to using, as well as BeReal and Google Maps, as they possessed many features that our users desired.
- Facebook
- Most favoured for big events
- Said to be too busy
- Most people have it muted
- Instagram
- Most favoured for casual communication & sharing photos
- "Not for genuine conversations"
- Lacks live locations or updates
- Whatsapp
- Lacks clear mode of availability or 'online status'
- Just for calling
- Favourable for video calling, as it is best for connectivity
- Bereal
- No real conversation
- Good for seeing where someone is and how they're doing
- Shows live time & location
- Google Maps:
Location Sharing - Live location sharing
- Lacks any form of communciation
- Not meant for conversations
One of the biggest common factor among all these social medias is...
You have no way of knowing when it isto contact someone.
This was our point of difference with GlobeChat. We wanted to finda way around the guesswork of communication. It is not attempting to compete with any of these other social medias, but in conjunction with it.
The three most explored ideas were the following:
Globe Wall Portal
A screen to have in your home that can show where loved ones are, how their doing and when they're free.
Voice Home-Assistant
A device that gives updates and relayed summaries of messages/social media updates
Multimedia Phone Game
To encouraged conversation through prompts, low-level passive touch and communication
At this point we needed to take a step back and consider the actual user needs. What were these ideas offering?
We conclusively decided to explore Globe Wall Portal further as the strongest solution. The reason why the home-assistant device and the cross-platform multimedia game ideas were scrapped was because they didn't alleviate the any actual pain points or offer a better solution than current systems already in place.
From here, we further visioned and sketched out the idea of GlobeChat Portal.
CONcept feedbacks & setbacks
As a team, we created the initial design proposal of the GlobeChat Wall Portal. The main idea was to have a visual globe depicting your loved one's whereabouts. You could install the portal in your home on the wall, perhaps in acrylic glass as a projection, or a screen, or we even explored the idea as an idle screen for your TV.
As a team, we presented our ideas to our tutor, and these are some selected slides that were used in our presentation.
We combine two high importance ideas together, being able to see a joint social calendar/visual globe, as well as quick and immersive experience for those who need personal touch.
The idea would take seeing 'availability' one step further, and have quick access buttons of want to speak or don't want to speak. You can access it through an app and the wall portal.
During a feedback session after our team presented our GlobeChat idea to our tutor, she asked us a question that left me stumped mulling over it for the better part of a week as it was such a blaringly obvious roadblack. She asked the following:
If GlobeChat's signature 'hero' product is the wall portal that differentiates it from others in the market, but in the user's journey the app can be used as a standalone, how do we anticipate to build a userbase strong enough to be satisfied with just using the app?
This was such an important aspect we had overlooked, as I realised it created a weak bottle-neck for incoming users. If we couldn't entice users to the app, then we wouldn't even be able to get them to the wall portal. From here considering the scope and timeline I had left of the project (3 weeks), I had 2 choices:
- Remove the app, and focus solely on the GlobeChat Wall Portal and redesigning it's marketability, desirability and viability
- Remove the Wall Portal and focus on the app, and ideate how to implementing the novelties of the wall into the app, and strengthen the marketing stand-point and gaining a userbase for the app
In the end, I decided to focus on the app, and leave the potential for expansion to the Wall Portal as a future implication and room for growth. An app on your phone is more easily accessible than installing a propduct on the wall. It also didn't make sense to try to make the wall portal work if gaining a userbase was going to be a heavy focus for the product.