The current implementation uses a button at the bottom of the article view to get the user to the original page using the in app browser.
The solution that inoreader uses is a scroll trigger when the user reaches the end, that opens the browser with a vibration feedback.
I think this is a better user experience than just a button.
The current implementation uses a button at the bottom of the article view to get the user to the original page using the in app browser.
The solution that inoreader uses is a scroll trigger when the user reaches the end, that opens the browser with a vibration feedback.
I think this is a better user experience than just a button.