TOKENIZED communities and Fixing our UX!

I mentioned it in a few of my other posts that arent related to marketing but this is a story I want to keep going for a simple reason.

TOKENIZED COMMUNITIES NEED TO BE THE FUTURE OF HIVE!

And I will be repeating this where ever I can. I will DM you, I will call you at work, I will knock on your door and ask you:

Have you heard about our lord and savior "Tokenized Communities?"

Ive been working on marketing for a few months now and in that time ive seen what exact problems Hive is facing. And its not the problems you might think. All of them seem to be related to user experience and community content valuation.

1. Regular users in any large amount will NEVER jump through the hoops of Hive account creation or put in effort to store, understand the bunch of passwords we have. THAT WILL NEVER HAPPEN IN A MILLION YEARS! Stop viewing the signup process from the point of view of a hiver. View it from the point of view of a random uninformed visitor!
   SOLUTION: Login through email/facebook and frontend seamless account custodial services.

2. Long form content has been for years the basis of how we assigned value to content. That kept us in our small niche and away from mainstream adoption. Not every person can write a 500 word blog but every idiot can write a 500 character tweet.
   let me illustrate what I mean.
   Out of 1000 clicks I got on our LinkTree yesterday. https://linktr.ee/_Hive.io

35% clicked on the Hive account@ecency "Download Mobile APP".

25% clicked on the Hive account@hiveonboard "Sign Up Here"

3% clicked on the Blogging option! Only 3%! (I removed the option afterwards.)

You will not get the mainstream to use Hive through blogging. We need to move away from blogging. It needs to be a niche even on Hive.

SOLUTION: Move everything to second layer which will allow for short form content to thrive while being able to compete with existing dapps.
Right now, no dapps offering short form content can compete with Hive account@peakd, Hive account@ecency, Hive account@hiveblog because the community views short form content as junk. Once "COMMUNITY TOKENS" are a thing then each dapp will have their own token and each will be able to compete regardless of content form.

It is clear at this point in time that Frontends and investors arent keen in having HiveEngine integrated. Im eagerly waiting for Hive account@threespeak to unveil their idea of community tokenization.

What ever comes first. SMTs or the 3speak system, there is only 1 thing that matters.

It needs to be a plug and play modular system with preset templates for content type that can be set up in 3 clicks by the most basic of users with 0 (ZERO) dev skill required. Token exchange built alongside it.

This is the future I see.

A Hive where frontends care most about user experience at all levels, where users can start using Hive without requiring any special knowledge or effort. Where anyone can create any community with their own token and economy in 3 clicks. Once we achieve that, we will thrive.