We started talking about this topic a few days ago when I shared the advantages of Inleo compared to other social media platforms I've used, both centralized and Web3. You can catch up on the first part of the discussion in my previous post.
Even though I'm new to Inleo, the seven days I've spent here have been enough to discover many things about both the platform and Hive in general. My first day on Inleo was great - everything worked smoothly. I must confess that my experience so far has been explorative and full of discovery and learning.
As I mentioned in that post, no platform is optimal in terms of perfection. Just as we have the good side, there are also drawbacks, but we need to create a balanced view of both sides. This isn't meant to critique the Inleo platform but to bring attention to those technical challenges that may have escaped the knowledge of the developer and platform team.
First, let's talk about logging in and signing up with Keystore. Using keystore to sign up for a Hive account made onboarding easier, with just a username and an encrypted password. However, this process isn't without its drawbacks.
Using the keystore sign-up/sign-in to Inleo limits users from exploring the Hive ecosystem - it restricts us to just Inleo. This means we cannot access any other Hive platform or frontends, as they call them.
The keystore wallet comes with a file that can only be used for accessing Inleo. Now, if we want to use the Hive wallet on the platform, we need a key to sign transactions. The same applies if we want to explore other Hive platforms. How do we get these key(s)? This is something the Inleo Developer(s) should look into as soon as possible.
Most activities on Inleo happen in the microblogging section, where users engage and interact through short posts. Given the importance of the microblogging section to the platform, I'd like to say that the functionalities are far below what I envisaged before joining.
From my experience using Threads during these seven days, there have been many moments of frustration because things don't work as expected. Most times, threads don't post - they just hang there as the post button keeps spinning endlessly. Even when I changed data networks, the result remained the same. This has really prevented me from engaging on the platform as much as I wanted.
This experience isn't limited to threading - the same thing happened with long posts, and it was even more frustrating as it took me over 2 hours to get my post published, trying over and over again.
A situation like this can be very frustrating for a newbie who lacks patience. Inleo needs improvement on this to allow everyone to engage at their optimal best. You know what they mean by "first impressions count"? A newbie testing the platform wants to see how smooth the UI is before making a commitment.
There's also the issue of threads not indexing, especially when you want to reply to older threads. Clicking on a thread usually brings up the message "The Thread is not indexed yet." I've had to keep refreshing the page whenever I experience this before the thread would load normally for me to read and reply.
I know this isn't a big deal, yet it can be frustrating to keep seeing it over and over again. And there are people who never knew that refreshing the page can make it load normally.
What do I score Inleo? For now, I would give it a 6/10 rating, and I hope the platform can improve on these technical drawbacks going forward. I know this report may not reflect what other newbies like me have experienced on the platform.
This experience nonetheless hasn't derailed my commitment one bit, as I'm yet to discover the full potential of Inleo, which I regard as a door to endless opportunities.
As I keep progressing on the platform, I'll keep updating my experiences. That will be all for now. Keep following my posts to stay updated about my progress.
Thank you for reading my post.
