Steemia is a social network app running over the Steem Blockchain. This app will provide the users an enriched user experience plus features commonly encountered in a casually used social media. The goal of this project is to give the community a mobile app where they can do their daily activity in the blockchain.
In depth nested pages the edit comment page was not working due to a bad parameter being passed. This error was fixed by tracking the the origin of the page to determine the correct parameter.
After unvote, it was dispatched correctly but there was a weird issue because even if your vote is 0% is still shows as vote. To avoid this behavior, I modified the server side logic to remove voters with 0 weight from the "is voted" post checker. Also, to compensate this modification, the voters list was filter out to remove 0 weight votes as well.
After seeing the comments of various users in our introduction post, we determined that a dark UI was a must according to them. Hence, I decide to start working in the dark UI and here are the results:
This UI can be activated through settings page.
Before, the bookmarks page was empty when there were not bookmarks. This can lead to confusion of the page not being loaded or a bug in the app. The following message was added to avoid any confusion:
After seeing the comment of one of our users, I noticed that an elastic textarea was a must. Before, this user made a suggestion because it was so hard to edit a long post in an static textarea. Hence, I decide to implement the elastic one to allocate height dynamically based on the text.
There were not possibility of uploading a picture in comment box. However, thanks to one of our users, this is now possible.
Some users were confused on how to insert tags in our application. It clearly says that it should be separated by comma. However, most of the users are already accustomed to separate them by space like in Steemit and other Steem frontends. So, I decide to keep both ways so users that are accustomed to put the comma can still keep doing it in the same way.
Some users though that it was a bug in our application. However, it was not implemented yet. Now, you can easily access your followers/following profiles within the list.
The save button in the settings page was making an extra step to the user. This data can be saved automatically on changes. Hence, I decide to eliminate this button and allow data to save automatically.
Since we were writing the same code across page, I saw a good case for reusability of code. Thus, all the logic to capture photos, take photos from gallery, and upload image to server side were moving to a separated provider which can be called from any page. The usability of the provider is easy since all the methods return a promise with the url of the uploaded image.
When you save a bookmark, an alert was shown (which is annoying). What I did was replace this alert with a toast to avoid user action to dismiss the alert.
In the users search feature, we didn't have an auth guard to prevent dispatching actions if the user is not logged in. By default, we show the follow button for the results. When an user is not logged in, the button is still shown there. When you press this button, it changes to unfollow meaning that the action can be dispatched (even though it was not dispatched). To avoid this behavior, an alert is now shown to tell the user that this action requires you to be logged in.
Steemia is open source and it will always be 馃檭. If you would like to contribute to this project, feel free to fork the Steemia repo and send us a Pull Request.
