One thing that happened later was a bug in the HivePulse.app related to how the KE was calculated. I got the feedback on this thtough a comment to an old post as the app doesn't offer a way to provide feedback. Why it doesn't? Because I designed the app not to rewuire any Hive login and just use it passively without any worries of authentication integration. But as community voice is important, I thought of doing a widget that redirects the user to a post on PeakD acting like a container to gather feedback. This will allow collecting anything that a user wants to request or ask about the app without feeling that he or she needs to do another login. We have quite many and good interfaces on tbe hive blockchain and I didn't feel we needed another one.
Besides gathering and providing feedback, the container post for the hivepukse.app will be created on a weekly basis and will allow users show any form of support for the project as well: tipping, upvoting etc. I don't want this to be intrusive and just redirecting the user to a well established interface should keep that trustworthy.
This is not a big feature by any means, but I think it is something that was needed. Having a communication channel with the end users right from the app increases usability, visibility and facilitates a way of improving it through the voice of the community. Just a light widget that does automatically a redirect to the latest app feedback container. Simple and with no other hassle. It is there, if something is bothering you or if you want a new feature, just click on it, you'll be redirected to an article for collecting feedback, write a comment and it will be considered.
I went for a weekly container post in order to enable fresh feedback on the app, alongside with an upvote and tipping for of support for the project given on the article for the 