You like the news and want to tweet about it? Press Menu, Press the "t" icon. (If you are not logged in, you will be asked to do so first time). You will get a box to type your twit, while the URL is getting shortened in background. After the short URL is ready, insert it (with/without news title). Edit the twit if you want to and hit Post.
Now about the problem mentioned in Market comments:
There was a bug in beta1 that manifested itself in terms of empty lists. If the user presses "Refresh" on first screen and tries to visit a feed he/she has tried to read before hitting refresh; then they will end up with an empty list - with only the title on the top and an unread count. This problem was fixed in beta2. But if you upgraded from beta1 to beta2, the old database stayed unchanged and you will again see the problem. Therefore, if you tried beta1 and are now trying beta2/3, just make sure you uninstall beta1 first.
If you still find any problem in this or other area, please post here on the blog OR tweet me (@jyro). If you post on the Android Market, I will be able to read it (via cyrket), but I haven't found a way to post my comments to the Market. I believe the only way is through the Android Market app on phone (which I don't have at this point). I have managed to communicate through the Package description a bit, but it's a very crude work around with 325 char limit. So try to post here.
Enjoy the beta3!
4 comments:
I've been trying all the rss readers for android, hoping one will actually work for me. I'm looking for google reader syncing and good offline support. ReaderScope comes close! Keep up the good work.
Unlike GReed and newsrob, you seem to do the google reader syncing correctly. But offline reading needs more work. Images are missing, it complained about not being able to update the read count, and then hung trying to load tags. Had to powercycle the phone.
> But offline reading needs more work. Images are missing, it complained about not being able to update the read count,
Yes, offline reading is an important aspect. I will be focusing on it more.
> and then hung trying to load tags. Had to powercycle the phone.
I see. Could you tell me, if your phone was offline since before you started readerscope, OR was it online when you started the app and after a while it lost network connectivity?
In any case, the app freezing is not excusable; but your answer will help me understand the scenario better.
Thanks for the feedback!
The phone was online, then I told it to download, then I switched off the network to test -- all while the app was running.
> The phone was online, then I told it to download, then I switched off the network to test -- all while the app was running.
Just as I suspected. Thanks for clarifying. This situation isn't handled well yet. If the app is offline at start, the rest of the operations are run in offline mode. If it was able to login at the beginning successfully, it assumes n/w access for rest of the operations. That's when it will go in long wait over network.
Definite room for improvement.
Post a Comment