My definitions: A feature is an embellishment which can make a product better, while the hook is the core experience that drives users to the product. Think of features as the asterisk icons on the back of a video game box. 2/10 
A friend pitched me an app idea using shared identity across apps with addictive ad-clicking behavior for revenue. He said he would play that all the time on his phone to level up. I asked “play what?” He had no answer because he focused on the features but not the hook. 3/10
I hear similar feelings around social & multiplayer all the time (see first image in thread). Shared presence is in my mind the most critical feature for #XR experiences at this stage in the industry. 4/10
At the end of the day though, while multiplayer makes a great demo showing the possibilities of the future, on its own it is ultimately still just a feature. 6/10
But when looking at features, it’s easy to forget that shared identity, multi-user, and aligned AR presence still need to supplement a core hook: A reason for being there. 8/10
My go-to analogy involves purse hangers at the bar. It’s a wonderful feature for the patrons. But if the drinks or ambiance (core hook) aren’t good, then this embellishment doesn’t matter because the customers won’t be back. 9/10
It’s easy to mislabel a demoable feature as a product, especially in #XR w/so many ideas to experiment with. If you’re making content, keep this in mind.
Focus on the core. Embellish with the features.
Don’t mistake one for the other, & use both wisely to success.
Fin. 10/10
Focus on the core. Embellish with the features.
Don’t mistake one for the other, & use both wisely to success.
Fin. 10/10
