The original mobile Reader interface is clearly much better than the
new iPhone one -- quicker to load/refresh, and it reformats 'original
versions' and linked-to pages into a mobile-friendly format. This was
the best thing about it.
However I can't view it any more on my iPhone.
When I go to http://www.google.com/reader/m I get redirected against
my will to /reader/i -- please tell me there's a workaround! Otherwise
mobile Reader has been pretty much ruined for me.
Not all of us have 3G iPhones (http://www.geekculture.com/joyoftech/ joyarchives/1125.html), so the reduced loading time via the original
interface was really important. But more importantly, it made pages
MUCH easier to read, and this is still true on the 3G version.
I really hope it's not that Google have come under pressure from
advertisers who didn't like seeing their ads getting stripped out.
As posted in another thread, if this is not promptly changed I'll be
ditching Google Reader for good. This is awful how very little
reading I get done on my iPhone now. If Google doesn't give us page
reformatting options back, I am sure another decent reader will become
available in the App Store at some point and I will make the switch.
One way or another (3G or not) the interface as it stands is useless
to me now.
> As posted in another thread, if this is not promptly changed I'll be
> ditching Google Reader for good. This is awful how very little
> reading I get done on my iPhone now. If Google doesn't give us page
> reformatting options back, I am sure another decent reader will become
> available in the App Store at some point and I will make the switch.
Does it still work on other phones? If so, maybe jailbreaking the
iPhone and changing the user agent would work. But that seems like
overkill...
It doesn't seem that there's a way to change the user agent even after
jailbreaking. I searched around and saw a suggestion of using a proxy
like Anonymouse.org but I haven't tried that yet and I'm not sure that
would work well with the ping-happy Reader.
> > As posted in another thread, if this is not promptly changed I'll be
> > ditching Google Reader for good. This is awful how very little
> > reading I get done on my iPhone now. If Google doesn't give us page
> > reformatting options back, I am sure another decent reader will become
> > available in the App Store at some point and I will make the switch.
> Does it still work on other phones? If so, maybe jailbreaking the
> iPhone and changing the user agent would work. But that seems like
> overkill...
problems are from last weekend, but still no answer from google reader
team :(
why google reader team didn't announced such big change? why this
changes without warning?
I'm big google reader user since I get iPhone, because it was easy
with google reader and GWT read all my watched feeds, but now it's
horrible SLOWER and when I want to see whole article it displays
original page (why?) without previous GWT formatting and even without
option to set it like it was before.
Please someone from Google Reader Team to answer this.
do people from the google reader team actually read this thread? if so
are they too overwhelmed with email to reply? if not, it would be
really great to get even just a quick message like "yes, we see your
issue and are working on it" or "sorry, WYSIWYG, forever." at least
then we could all move on. ug.
> The original mobile Reader interface is clearly much better than the
> new iPhone one -- quicker to load/refresh, and it reformats 'original
> versions' and linked-to pages into a mobile-friendly format. This was
> the best thing about it.
> However I can't view it any more on my iPhone.
> When I go tohttp://www.google.com/reader/mI get redirected against
> my will to /reader/i -- please tell me there's a workaround! Otherwise
> mobile Reader has been pretty much ruined for me.
> Not all of us have 3G iPhones (http://www.geekculture.com/joyoftech/ > joyarchives/1125.html), so the reduced loading time via the original
> interface was really important. But more importantly, it made pages
> MUCH easier to read, and this is still true on the 3G version.
> I really hope it's not that Google have come under pressure from
> advertisers who didn't like seeing their ads getting stripped out.
I am using Nokia e61 phone and recently it started to show iPhone
version of Google Reader (even if I go to reader/m). For me it made
mobile version of Google Reader almost completely unusable:
- it takes longer to load (it is about 200k)
- browser uses too much memory, so I can not start other applications
at the same time
- it is almost impossible to view more than 30 items - browser becomes
slow
- items are not marked as read even after I read them
So please let me use the old version. It was much more usable on my
phone.
> The original mobile Reader interface is clearly much better than the
> new iPhone one -- quicker to load/refresh, and it reformats 'original
> versions' and linked-to pages into a mobile-friendly format. This was
> the best thing about it.
> However I can't view it any more on my iPhone.
> When I go tohttp://www.google.com/reader/mI get redirected against
> my will to /reader/i -- please tell me there's a workaround! Otherwise
> mobile Reader has been pretty much ruined for me.
> Not all of us have 3G iPhones (http://www.geekculture.com/joyoftech/ > joyarchives/1125.html), so the reduced loading time via the original
> interface was really important. But more importantly, it made pages
> MUCH easier to read, and this is still true on the 3G version.
> I really hope it's not that Google have come under pressure from
> advertisers who didn't like seeing their ads getting stripped out.
Thanks for your feedback on the recent changes to Google Reader for
your iPhone. Could you all confirm that you are using the latest
version of your iPhone's firmware? The latest update offered by Apple
improves performance significantly and using Google Reader should not
cause poor performance, even on EDGE iPhones.
I'd also like to let you know that we hear your feedback loud and
clear regarding allowing the original, HTML version of Reader on your
iPhone as an option. I'll post an update to this situation shortly. In
the meantime, please let me know if updating to the latest version of
your iPhone's firmware doesn't solve the issue.
> Thanks for your feedback on the recent changes to Google Reader for
> your iPhone. Could you all confirm that you are using the latest
> version of your iPhone's firmware? The latest update offered by Apple
> improves performance significantly and using Google Reader should not
> cause poor performance, even on EDGE iPhones.
i'm using the latest firmware on BOTH my phones (one EDGE, one 3G) -
and the loadtimes for the original HTML versions is SLOOOOOOW - to the
point i've stopped reading my feeds on my phone.
I'm using 2.0 and for me the speed is fine, it's that i just want to
use the old version - for many reasons stated by others in this and
the other threads, but most especially because the old version showed
all feeds in a given category together. i don't want to see my feeds
broken down by individual source, it's extra clicks navigating to and
back from feeds.
thanks
> Thanks for your feedback on the recent changes to Google Reader for
> your iPhone. Could you all confirm that you are using the latest
> version of your iPhone's firmware? The latest update offered by Apple
> improves performance significantly and using Google Reader should not
> cause poor performance, even on EDGE iPhones.
> I'd also like to let you know that we hear your feedback loud and
> clear regarding allowing the original, HTML version of Reader on your
> iPhone as an option. I'll post an update to this situation shortly. In
> the meantime, please let me know if updating to the latest version of
> your iPhone's firmware doesn't solve the issue.
I am using 3G iPhone, and yes the performance of iPhone version of the
reader is ok, BUT only if my 3G connection is stable. My point is, not
everyone is using iPhone is having fast and stable connections. So all
we need are the following options to be available :
1. We should be able to switch back to the old html mobile version
2. For iPhone version, we should be able to set the option to reformat
the external link (the view original source link) to mobile version,
just as what the old html version has.
There are 3 reasons why we need option (2) above even for fast 3G
iPhone:
i) After viewing an external page in full version in a new tab, when I
close the tab to return back to google reader, the mobile Safari
usually will reload the google reader page , most probably due to
memory limitation. This won't happen previously when the external page
is reformatted to mobile friendly format. This is not what the
original iPhone google reader interface design want to be, isn't it?
ii) Even worse, if the external page contains some more extra images,
mobile Safari can crash.
iii) Even more worse, when I try to relaunch mobile Safari after a
crash, sometimes Safari simply forgot the external page link that I
just viewed. It usually will only open back the google reader page.
But since the external page link is already marked as "read", it won't
show up in the "new feeds" view. I have to switch back to "all feeds"
in order to get the link back.
Suggestions to update iPhone firmware are useless to those of us using
other devices, such as the Nokia N95 in my case, which also have not
been able to access the much preferred http://www.google.com/reader/m/ site. The /m site still works in a full browser and on other mobile
devices such as the Nokia N800/N810.
As someone posted on another thread, the full user agent for the N95
looks like:
Why the N95 advertises itself as Safari, I'm not sure -- couldn't find
much information on this.
Please, turn off the redirect so the mobile version of Reader is
useful again, and kindly point whoever made the decision to force /m
users to the /i page to the Google Code of Conduct:
http://investor.google.com/conduct.html
> I am using 3G iPhone, and yes the performance of iPhone version of the
> reader is ok, BUT only if my 3G connection is stable. My point is, not
> everyone is using iPhone is having fast and stable connections. So all
> we need are the following options to be available :
> 1. We should be able to switch back to the old html mobile version
> 2. For iPhone version, we should be able to set the option to reformat
> the external link (the view original source link) to mobile version,
> just as what the old html version has.
> There are 3 reasons why we need option (2) above even for fast 3G
> iPhone:
> i) After viewing an external page in full version in a new tab, when I
> close the tab to return back to google reader, the mobile Safari
> usually will reload the google reader page , most probably due to
> memory limitation. This won't happen previously when the external page
> is reformatted to mobile friendly format. This is not what the
> original iPhone google reader interface design want to be, isn't it?
> ii) Even worse, if the external page contains some more extra images,
> mobile Safari can crash.
> iii) Even more worse, when I try to relaunch mobile Safari after a
> crash, sometimes Safari simply forgot the external page link that I
> just viewed. It usually will only open back the google reader page.
> But since the external page link is already marked as "read", it won't
> show up in the "new feeds" view. I have to switch back to "all feeds"
> in order to get the link back.
I have a 1st gen iPhone running the 2.0 software update, and I agree
with all the above sentiment.
I don't mind if you want to change the default to be the whizzy new /i
version, but give me the option to switch back to /m -- frankly, I
just like the interface better, and it's much snappier on low-
bandwidth EDGE connections (plus the mobile-reformatting option makes
some things much easier to read).
> I have a 1st gen iPhone running the 2.0 software update, and I agree
> with all the above sentiment.
> I don't mind if you want to change the default to be the whizzy new /i
> version, but give me the option to switch back to /m -- frankly, I
> just like the interface better, and it's much snappier on low-
> bandwidth EDGE connections (plus the mobile-reformatting option makes
> some things much easier to read).
I tho i was alone....I too dislike the new /i version. Please bring
back the previous version ASAP!
It's incredible slow even over 3G and it just not fun reading the
feeds on the go anymore.
> I can not agree more. Please give us back the old interface. Much
> snapier on iPod Touch as well
> On Jul 20, 10:47 pm, Steven Johnson wrote:
> > I have a 1st gen iPhone running the 2.0 software update, and I agree
> > with all the above sentiment.
> > I don't mind if you want to change the default to be the whizzy new /i
> > version, but give me the option to switch back to /m -- frankly, I
> > just like the interface better, and it's much snappier on low-
> > bandwidth EDGE connections (plus the mobile-reformatting option makes
> > some things much easier to read).
> I tho i was alone....I too dislike the new /i version. Please bring
> back the previous version ASAP!
> It's incredible slow even over 3G and it just not fun reading the
> feeds on the go anymore.
I hate to add a ditto post, but I do want to let the Google Reader
team know that I am using 2.0 firmware update on my new 3G iPhone, and
I am very unhappy with the new Google Reader interface. (My biggest
pet peeves being the auto refresh when returning back from a news
article, loosing my place and the lack of GWT formatted pages.)
> I couldn't agree more. The html version was a pleasure to use. The new
> one is quite a bit painful.
> On Jul 22, 3:18 am, Sodium wrote:
> > I tho i was alone....I too dislike the new /i version. Please bring
> > back the previous version ASAP!
> > It's incredible slow even over 3G and it just not fun reading the
> > feeds on the go anymore.
> Suggestions to update iPhone firmware are useless to those of us using
> other devices, such as the Nokia N95 in my case, which also have not
> been able to access the much preferredhttp://www.google.com/reader/m/ > site.
I'll second this: I use a Nokia 6120c, which is a Symbian S60 phone. I
was reasonably happy with the original mobile version of reader, and
actually quite like the first iPhone version as it was usable on the
S60 browser. But the new iPhone version is pretty much unusable and as
a result I'm hardly using Reader mobile at all now. Problems:
* Always starts up with the 'All Items' reading list. As a result the
item list is full of items from high-volume feeds like TechCrunch.
* Selecting 'Feeds' and then clicking on a tag leaves me at a blank
page. From going to http://www.google.com/reader/i with Firefox I can
see what should be happening, but the list of feeds within a tag
doesn't get populated.
* I also find that article links from the mobile iGoogle Reader gadget
don't work either: the article seems to get marked as read, but the
reader interface just brings up the 'All Items' reading list, not the
article that has been clicked on.
Another +1 - reformatting pages through GWT was the one compelling
reason to use Google Reader on the iPhone.
Great to see from the above that Google have taken this feedback on
board - looking forward to actually being able to use the Google
reader again once it's fixed.
ok. I was trying to use this "new" iPhone reader and here is my
opinion.
I have 1.1.3 FW still on my iPhone, because I have no time for
"testing" new 2.0 FW yet, but afaik safari is still in the very same
version.
1. new reader is much more usefull than old one. it has some cool
features like:
- perex visible on the same page
- more options to share articles (like in full version)
- better options to mark it as read
- option to view specific feed
- option to view already read items in reader or even in the specific
feed
- speed of "application" is almost as good as it was
2. GWT is missing
there is no option to view whole article through GWT (i dunno if it is
right name for this feature, but i guess so) unlike on the old
version. there is only view original and it is (on EDGE) "pain in the
ass". please give this feature back at least as option.
3. "broken" view after refresh
there are some situations after refresh when I'm not able to view
whole reader, but when I use safari built in refresh button, it
repairs. it's annoying, because I need to wait for whole reader to
load :(
there is another way how to fix it. more quicker, but it not worked
every time unlike Safari refresh. when tap headline, from whatever is
visible right now, to get a perex, than reader loads almost all
"hidden" headlines without reloading whole reader. see screenshots:
http://picasaweb.google.com/krocek/IPhoneGoogleReaderError
4. too wide articles in reader
when "publisher" decides, that you will get whole article after tap on
headline (no perex, whole article after headline), sometimes formating
in reader is too wide and i must scroll also horizontally to read it :
( but also rest of the reader "goes wide" and other articles after
this whole one are wide also :( until next "mark it as read" action.
only solution is to read it in wide mode, so in fact is not that
"serious", but only annoying.
screenshots are available also: http://picasaweb.google.com/krocek/IPhoneGoogleReaderError
hope it will help you and hope you will "understand" (it's another way
how to say: sorry for my english :)
> Thanks for your feedback on the recent changes to Google Reader for
> your iPhone. Could you all confirm that you are using the latest
> version of your iPhone's firmware? The latest update offered by Apple
> improves performance significantly and using Google Reader should not
> cause poor performance, even on EDGE iPhones.
> I'd also like to let you know that we hear your feedback loud and
> clear regarding allowing the original, HTML version of Reader on your
> iPhone as an option. I'll post an update to this situation shortly. In
> the meantime, please let me know if updating to the latest version of
> your iPhone's firmware doesn't solve the issue.
I have a 3G, am running the latest firmware, and the /i is just lousy
web 2.0 eyecandy. Please turn the /m back on. Numerous reasons are
listed in this thread and others; you guys mean well, but you're over-
thinking what we want. Lots of readers out there suffer this same
fate; we want something simple, clean, reliable, consistent. The new /
i is none of these. Take care of us.
> Thanks for your feedback on the recent changes to Google Reader for
> your iPhone. Could you all confirm that you are using the latest
> version of your iPhone's firmware? The latest update offered by Apple
> improves performance significantly and using Google Reader should not
> cause poor performance, even on EDGE iPhones.
> I'd also like to let you know that we hear your feedback loud and
> clear regarding allowing the original, HTML version of Reader on your
> iPhone as an option. I'll post an update to this situation shortly. In
> the meantime, please let me know if updating to the latest version of
> your iPhone's firmware doesn't solve the issue.
I really missed the OLD reader. I used to love Google read before
they changed to new version in mid July.
Google, please bring back the old one that can convert to mobile
version via "GWT", for mobile users, this saves us a lot of $$.
Loading full HTML is slow and expensive.
> The original mobile Reader interface is clearly much better than the
> new iPhone one -- quicker to load/refresh, and it reformats 'original
> versions' and linked-to pages into a mobile-friendly format. This was
> the best thing about it.
> However I can't view it any more on my iPhone.
> When I go tohttp://www.google.com/reader/mI get redirected against
> my will to /reader/i -- please tell me there's a workaround! Otherwise
> mobile Reader has been pretty much ruined for me.
> Not all of us have 3G iPhones (http://www.geekculture.com/joyoftech/ > joyarchives/1125.html), so the reduced loading time via the original
> interface was really important. But more importantly, it made pages
> MUCH easier to read, and this is still true on the 3G version.
> I really hope it's not that Google have come under pressure from
> advertisers who didn't like seeing their ads getting stripped out.
|
