Going to kick this version off with some cache improvements to smooth out the experience. Then I will move on to other features on the roadmap.
Changes so far (may be regularly updated):
- Cache user subscriptions. User subscriptions will continue to refresh on app load, however a cache will always be shown.
- Fix a bug where “set as home” will not work if the user is already on the home “tab”. (Fun fact, the app treats each community on the left pane as a “tab”. Each tab actually has it’s own history).
- Change the behavior of the home button. If the home button is tapped when you are at the top of page 1 of a community page and you are not on your home page then you will be taken to your home page.
- Added the ability to create, edit or delete posts.
Update
Going to roll this out to beta. I will roll out to release tomorrow morning. Good night!
deleted by creator
Yep I get it. This is a tough call. Both have their advantages. For instance, let’s say you are subscribed to c/memes. You are on page 3 you wanted to check if there were any updates. You can tap home to go back to page 1 and then pull to refresh to see new posts.
But there is also the use case you just want to go back “home” and not just go to the “home” of the current community. I think that’s the issue here. That are multiple “homes” here.
I think from a intuitive sense, your suggestion makes more sense. Tapping a button “home” should take me home which is my “home” community. I will need to think more about if I should also provide some easy way for users to go back to the top of page 1.
There is the “crazy” option to make it so if you tap home while ur at the top of page 1 of a community, it will take you to your home community. This will give users flexibility on where they want to go based on single vs double tap. Whether this will be intuitive to users is another issue.
I implemented the tap twice to go to “home home” feature for the next update. If it solves the problem and doesnt feel awkward to use we can leave it like that.