Boosting Engagement & Improving User Activity : The Role of Dynamic Resource Credits on Inleo
Hello all #LEO Lovers and #Hive Friends
Inloe team is working hard to onboard new users to the platform and their is no doubt that the same. The onboarding is one aspect only the other aspect is the activity on platform. If we onboard a hundred of new users to the platform but if unfortunately a few numbers only use the platform by creating a post, or a thread or commenting on other long form posts then this is not a good condition. The users not posting or engaging with other users are considered as the non active users, which are ideal and not contributing at all for the growth of the platform. Those users are not participating in the monthly active users (MAU). If I am not wrong then the user must make at least one post or thread or a comment to be count in monthly active users. The major problem we are facing in my option in Hive ecosystem is retention of the new joined user base. The users are joining but not using the platform may be because of the lack of knowledge, lack of interest or may be because of lack of resource credits, or my be because of lack of motivation. As per my experience the motivation factor is double edge sward, because to motivate new user we use to show him or her the earnign potential from the platform and also shows the trending page. The trending page mostly shows the long form posts with more then average earning (mostly more then 10 USD). No doubt such posts also encourage them to use the platform and start earning. But the problem arise when the new user start posting and not received the response as expected. The small amount of upvote one major factor that the user start disliking the platform. Their expectations are high because they have seen the other posts form trending page earning much more then what the are getting for their posts. Here the conflict started and which leads to the inactivity of user. I am not blaming anyone here and consider the greed as major culprit. The greed of earning more without putting any value to the platform, by publishing one long form post without engaging with others is the mistake people do mostly. I was also done the similar mistakes. It always took some time to understand the mechanism and engaging with others is the best way to understand it and it also helps to grow your account by making friends here.
Dynamic Resource Credit Mechanism
In the above para I try to present my view which are person related, but I have seen that some people joined and they are so much active that they face problem of shortage of Resource Credits. This s system related problem and here users want to engage more but unfortunately when he joined he has a little Resource Credit and which allows him to do a little activities on platform. If you are not aware then I like to share that every action in Hive ecosystem requires some Resource Credit, here activity means the publishing any post, commenting on posts, upvoting / downvoting, reblog etc.
Any new user joined the Hive ecosystem through the Inleo platform got some delegation so that her or she may be able to interact on platform. The current system has a flat rate delegation that is sufficient for a users to make 20 blog posts a day, which are sufficient for a average new user. But if any user is active on threads he / she may required more Resource Credit and this is form my personal experience. The 20 threads in a day is not a big deal and any users if active of other social media platforms before joining the Hive may easily cross the numbers. One way to solve this problem is delegate more Resource Credit but this also means that the system will delegate the more Resource Credit by default to less active or no active users also. Which is not good solution as it may leads to more ideal Resource Credits.
So to solve this issue the Inleo team has come up with Dynamic Resource Credits option. This system will be based on the tracking mechanism, which means the system will track the user activity and delegate or pull back resource credits as per the requirement of the users. This will ensure that a new user will never run out of resource credits. This new system is very importance of solving the resource credit issue for new users and their goal to remove the need for users to worry about resource credits at all.
I appreciate the efforts by the Inleo team which enhance the user experience day by day. Form lite signup functionality for onboarding seamlessly new users to adding new feature like shorts, the team is very active and very efficiently address the feedback of users. I am also trying to onboard new users and that should be joint efforts only. The community movement only make this program successful.
This is my participation post for Initiative: August Monthly Prompt
Check the above link for more details.
What are your view let me know in comment section.
Let's Connect
Hive: @guurry123
Twitter: https://twitter.com/guurry123
Discord: guurry123
Posted Using InLeo Alpha
I like the idea of anything which encourages new users to get into the habit of being active. After a few months of regular activity, hopefully they'll see their account starting to really grow, which makes habitual activity worthwhile.
Something I'd love to see, which I think would especially help new users, is to significantly reduce or even remove the dust threshold for the LEO part of upvotes on Threads. Too often, I see only threads by really big names getting upvotes; in most other cases, people don't vote for other threads because it's perceived as a wasted vote. But if it still paid out LEO, then it might be seen as worthwhile.
But I appreciate it might complicate the Hive Engine economy in terms of transaction load, and might create a need to find a way to improve (or better distribute) witness funding for Hive Engine node operators.
that is good suggestions but I am aalso not aware how much load it will increase on system.
!BBH !ALIVE !HBIT
@alonicus! @guurry123 likes your content! so I just sent 1 BBH to your account on behalf of @guurry123. (1/5)
(html comment removed:
)