<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Twitterrific&#8217;s Tough Love</title>
	<atom:link href="http://gedblog.com/2010/05/20/twitterrifics-tough-love/feed/" rel="self" type="application/rss+xml" />
	<link>http://gedblog.com/2010/05/20/twitterrifics-tough-love/</link>
	<description>A day in the life of me.</description>
	<lastBuildDate>Sat, 19 May 2012 12:54:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Derek</title>
		<link>http://gedblog.com/2010/05/20/twitterrifics-tough-love/comment-page-1/#comment-38283</link>
		<dc:creator>Derek</dc:creator>
		<pubDate>Sun, 05 Sep 2010 16:08:56 +0000</pubDate>
		<guid isPermaLink="false">http://gedblog.com/?p=1813#comment-38283</guid>
		<description>I have not used twitterific in some time. After reading your post(s) and trying it out again I am impressed with v.3. The old app was confusing. V.3 is much more intuitive, seems easier to use and less maddening than the official client/tweetie (which has become more bloated of late). Your instapaper integration is the best I have come across. Seamless. Great work!</description>
		<content:encoded><![CDATA[<p>I have not used twitterific in some time. After reading your post(s) and trying it out again I am impressed with v.3. The old app was confusing. V.3 is much more intuitive, seems easier to use and less maddening than the official client/tweetie (which has become more bloated of late). Your instapaper integration is the best I have come across. Seamless. Great work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: river b</title>
		<link>http://gedblog.com/2010/05/20/twitterrifics-tough-love/comment-page-1/#comment-38178</link>
		<dc:creator>river b</dc:creator>
		<pubDate>Thu, 02 Sep 2010 22:48:55 +0000</pubDate>
		<guid isPermaLink="false">http://gedblog.com/?p=1813#comment-38178</guid>
		<description>i loved twitterrific 2 on my iphone so much. even though it lacked some of the recently added features that other clients have i persisted in using it right up until it was impossible to do so (oauth changeover). i have to say, i&#039;m immensely disappointed in v3 on the iphone. i absolutely respect your approach on this, and i understand your philosophy. if you lose some long-time users, so be it.

but i have to say, i think the app is dramatically *un-streamlined*. it may be more obvious, and i can see why that&#039;s a good thing. i&#039;m a web/ui designer, so i get it. i really do. but twitterrific was like an extension of my brain in a way i don&#039;t think the new version can be. it all comes down to too many taps and screens. going back and forth to see timeline, filter by @replies or dm&#039;s, etc. it&#039;s too much, and all the taps and little delays add up to a frustrating experience that feels laborious. it&#039;s not empirically a lot more time or effort, but it really feels like it.

a few examples of things i *loved* that are gone:

- tap on tweet to select it. i just want to select, i don&#039;t want to go to a new screen dedicated to that tweet. i&#039;ve never liked this behavior in any client. it takes the tweet out of context and has always seemed unnecessary. i want to *select* and then *act*. not select/slide/view options/choose option/act. it&#039;s subtle, but it&#039;s huge.

- filter from the menu bar. it&#039;s basic and a lot of clients use this approach. just makes sense to me. a separate view for timeline/replies/dms etc etc is perfect for the ipad when i can see both at the same time. not good on the iphone where i have to constantly go back and forth. there are three areas i want to look at very often and very easily, and now it&#039;s multiple taps that change screens to go between them.

- tweet/reply button. this was always one of my absolutely favorite features. it converts to a reply button when a tweet is selected, and the tabs to change what i&#039;m doing when composing were brilliant. it always felt seamless and like there was a great flow. like things folded elegantly into other things. power without undue complexity. that is lost.

- double-tap for conversations. again, a simple, elegant solution to allow the user to access a lot of information with little effort and little mental gear-shifting.

- wonderful ui touches. just delightful little details that always made me feel like i was using an app made by *someone*. it had character.

these are just some of the reasons i loved twitterific. and not only were these things well-done, many features in the app were unique to twitterific. i always thought it had a strong sense of style and an opinion, rather than being sort of cookie-cutter, like so many of the twitter clients are.

anyway, sorry to go on. i&#039;m looking for another client now, that will at least do some of these things in a similar fashion. i don&#039;t hold out much hope that i&#039;ll get closer than 75%, and there&#039;s nothing else with the style and flair of twitterrific, as far as i know. perhaps i&#039;m in the minority, but i&#039;m really going to miss the old bird.</description>
		<content:encoded><![CDATA[<p>i loved twitterrific 2 on my iphone so much. even though it lacked some of the recently added features that other clients have i persisted in using it right up until it was impossible to do so (oauth changeover). i have to say, i&#8217;m immensely disappointed in v3 on the iphone. i absolutely respect your approach on this, and i understand your philosophy. if you lose some long-time users, so be it.</p>
<p>but i have to say, i think the app is dramatically *un-streamlined*. it may be more obvious, and i can see why that&#8217;s a good thing. i&#8217;m a web/ui designer, so i get it. i really do. but twitterrific was like an extension of my brain in a way i don&#8217;t think the new version can be. it all comes down to too many taps and screens. going back and forth to see timeline, filter by @replies or dm&#8217;s, etc. it&#8217;s too much, and all the taps and little delays add up to a frustrating experience that feels laborious. it&#8217;s not empirically a lot more time or effort, but it really feels like it.</p>
<p>a few examples of things i *loved* that are gone:</p>
<p>- tap on tweet to select it. i just want to select, i don&#8217;t want to go to a new screen dedicated to that tweet. i&#8217;ve never liked this behavior in any client. it takes the tweet out of context and has always seemed unnecessary. i want to *select* and then *act*. not select/slide/view options/choose option/act. it&#8217;s subtle, but it&#8217;s huge.</p>
<p>- filter from the menu bar. it&#8217;s basic and a lot of clients use this approach. just makes sense to me. a separate view for timeline/replies/dms etc etc is perfect for the ipad when i can see both at the same time. not good on the iphone where i have to constantly go back and forth. there are three areas i want to look at very often and very easily, and now it&#8217;s multiple taps that change screens to go between them.</p>
<p>- tweet/reply button. this was always one of my absolutely favorite features. it converts to a reply button when a tweet is selected, and the tabs to change what i&#8217;m doing when composing were brilliant. it always felt seamless and like there was a great flow. like things folded elegantly into other things. power without undue complexity. that is lost.</p>
<p>- double-tap for conversations. again, a simple, elegant solution to allow the user to access a lot of information with little effort and little mental gear-shifting.</p>
<p>- wonderful ui touches. just delightful little details that always made me feel like i was using an app made by *someone*. it had character.</p>
<p>these are just some of the reasons i loved twitterific. and not only were these things well-done, many features in the app were unique to twitterific. i always thought it had a strong sense of style and an opinion, rather than being sort of cookie-cutter, like so many of the twitter clients are.</p>
<p>anyway, sorry to go on. i&#8217;m looking for another client now, that will at least do some of these things in a similar fashion. i don&#8217;t hold out much hope that i&#8217;ll get closer than 75%, and there&#8217;s nothing else with the style and flair of twitterrific, as far as i know. perhaps i&#8217;m in the minority, but i&#8217;m really going to miss the old bird.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly U</title>
		<link>http://gedblog.com/2010/05/20/twitterrifics-tough-love/comment-page-1/#comment-38149</link>
		<dc:creator>Kelly U</dc:creator>
		<pubDate>Thu, 02 Sep 2010 03:29:58 +0000</pubDate>
		<guid isPermaLink="false">http://gedblog.com/?p=1813#comment-38149</guid>
		<description>+1 to the marking of tweets.  

Most irritating that I no longer have that function - I used to use it to flag interesting tweets that I wanted to go back to and look at in more detail if I had time.

I don&#039;t sync my devices, so I didn&#039;t care that it wasn&#039;t syncable.  Perhaps if I had Twitteriffic on my home computer I&#039;d be vaguely interested in the possibility, but I only sync with my Mac when I have new podcasts to download.</description>
		<content:encoded><![CDATA[<p>+1 to the marking of tweets.  </p>
<p>Most irritating that I no longer have that function &#8211; I used to use it to flag interesting tweets that I wanted to go back to and look at in more detail if I had time.</p>
<p>I don&#8217;t sync my devices, so I didn&#8217;t care that it wasn&#8217;t syncable.  Perhaps if I had Twitteriffic on my home computer I&#8217;d be vaguely interested in the possibility, but I only sync with my Mac when I have new podcasts to download.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corey J</title>
		<link>http://gedblog.com/2010/05/20/twitterrifics-tough-love/comment-page-1/#comment-38128</link>
		<dc:creator>Corey J</dc:creator>
		<pubDate>Wed, 01 Sep 2010 19:39:29 +0000</pubDate>
		<guid isPermaLink="false">http://gedblog.com/?p=1813#comment-38128</guid>
		<description>Ged:
Good to know that the feature will someday make a return. I&#039;ll gladly come back to use Twitterrific when the feature is available (and maybe sooner if I can&#039;t find a client that does this for me in the meantime. Like I said, I really like your product, you simply took out the feature that I liked most about it)

Not being able to sync between devices doesn&#039;t matter to me so much as the ability to use the &quot;marked tweets&quot; feature to view articles for later reading while offline. (so I wouldn&#039;t go so far as claiming the feature to be &quot;useless&quot;- I certainly found a use for it)

In my scouring the net for other clients that have this functionality, I found several people who were either looking for the same feature, excited that v2 had it or were dismayed that v3 lost it (I&#039;d be happy to link them to you if you need further proof that this feature is sorely missed from v3). 

And to the people out there that complain that the feature doesn&#039;t sync across devices: Honestly, isn&#039;t it better to have it and not need it than need it and not have it?

Thanks for your time, Ged!</description>
		<content:encoded><![CDATA[<p>Ged:<br />
Good to know that the feature will someday make a return. I&#8217;ll gladly come back to use Twitterrific when the feature is available (and maybe sooner if I can&#8217;t find a client that does this for me in the meantime. Like I said, I really like your product, you simply took out the feature that I liked most about it)</p>
<p>Not being able to sync between devices doesn&#8217;t matter to me so much as the ability to use the &#8220;marked tweets&#8221; feature to view articles for later reading while offline. (so I wouldn&#8217;t go so far as claiming the feature to be &#8220;useless&#8221;- I certainly found a use for it)</p>
<p>In my scouring the net for other clients that have this functionality, I found several people who were either looking for the same feature, excited that v2 had it or were dismayed that v3 lost it (I&#8217;d be happy to link them to you if you need further proof that this feature is sorely missed from v3). </p>
<p>And to the people out there that complain that the feature doesn&#8217;t sync across devices: Honestly, isn&#8217;t it better to have it and not need it than need it and not have it?</p>
<p>Thanks for your time, Ged!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Robertson</title>
		<link>http://gedblog.com/2010/05/20/twitterrifics-tough-love/comment-page-1/#comment-38117</link>
		<dc:creator>Will Robertson</dc:creator>
		<pubDate>Wed, 01 Sep 2010 13:17:10 +0000</pubDate>
		<guid isPermaLink="false">http://gedblog.com/?p=1813#comment-38117</guid>
		<description>+1 for bringing back marking tweets. Still find I am missing the feature since switching to T3 when it was released :-)</description>
		<content:encoded><![CDATA[<p>+1 for bringing back marking tweets. Still find I am missing the feature since switching to T3 when it was released <img src='http://gedblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ged</title>
		<link>http://gedblog.com/2010/05/20/twitterrifics-tough-love/comment-page-1/#comment-38115</link>
		<dc:creator>Ged</dc:creator>
		<pubDate>Wed, 01 Sep 2010 12:02:40 +0000</pubDate>
		<guid isPermaLink="false">http://gedblog.com/?p=1813#comment-38115</guid>
		<description>Corey,

We liked marking tweets too, although we were unsure how many users actually used that feature. We now know that there were quite a few. At any rate, if we had kept marking tweets but didn&#039;t have a way to sync them across devices, that would have been next to useless. Tweets you marked on your iPhone wouldn&#039;t show up as marked on your iPad. This would have led to more frustration for users and we would have been yelled at for this as well. Given that, we decided to remove marks until such time as we can get them synced across all devices. Then they&#039;ll most likely return.

Hope this helps.</description>
		<content:encoded><![CDATA[<p>Corey,</p>
<p>We liked marking tweets too, although we were unsure how many users actually used that feature. We now know that there were quite a few. At any rate, if we had kept marking tweets but didn&#8217;t have a way to sync them across devices, that would have been next to useless. Tweets you marked on your iPhone wouldn&#8217;t show up as marked on your iPad. This would have led to more frustration for users and we would have been yelled at for this as well. Given that, we decided to remove marks until such time as we can get them synced across all devices. Then they&#8217;ll most likely return.</p>
<p>Hope this helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corey J</title>
		<link>http://gedblog.com/2010/05/20/twitterrifics-tough-love/comment-page-1/#comment-38107</link>
		<dc:creator>Corey J</dc:creator>
		<pubDate>Wed, 01 Sep 2010 07:33:24 +0000</pubDate>
		<guid isPermaLink="false">http://gedblog.com/?p=1813#comment-38107</guid>
		<description>Ged:
The marking of tweets made lots of sense to me. I don&#039;t have an iPhone so I can&#039;t use a service like Instapaper when I&#039;m away from a wi-fi connection. I would refresh my feed in the morning, read it over on my commute to work and mark off tweets that I&#039;d want to check out later when I had a connection at home. 
Honestly, it was the thing that set your program apart for me from the others. 
I don&#039;t have the desktop client working so waiting for Mac support isn&#039;t important for me. Marking tweets for later perusal later on is. 

Since I shouldn&#039;t hold my breath for this feature&#039;s return, does anyone know of another ipod / iphone app for Twitter that will allow me to mark tweets off for later viewing? 
If it returns, I&#039;ll be back to using Twitterrific. I liked it. It was everything I wanted in a twitter app.,, Until you took this feature out.</description>
		<content:encoded><![CDATA[<p>Ged:<br />
The marking of tweets made lots of sense to me. I don&#8217;t have an iPhone so I can&#8217;t use a service like Instapaper when I&#8217;m away from a wi-fi connection. I would refresh my feed in the morning, read it over on my commute to work and mark off tweets that I&#8217;d want to check out later when I had a connection at home.<br />
Honestly, it was the thing that set your program apart for me from the others.<br />
I don&#8217;t have the desktop client working so waiting for Mac support isn&#8217;t important for me. Marking tweets for later perusal later on is. </p>
<p>Since I shouldn&#8217;t hold my breath for this feature&#8217;s return, does anyone know of another ipod / iphone app for Twitter that will allow me to mark tweets off for later viewing?<br />
If it returns, I&#8217;ll be back to using Twitterrific. I liked it. It was everything I wanted in a twitter app.,, Until you took this feature out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cris</title>
		<link>http://gedblog.com/2010/05/20/twitterrifics-tough-love/comment-page-1/#comment-35030</link>
		<dc:creator>Cris</dc:creator>
		<pubDate>Tue, 20 Jul 2010 22:46:11 +0000</pubDate>
		<guid isPermaLink="false">http://gedblog.com/?p=1813#comment-35030</guid>
		<description>I loved the old version (bought it)... I&#039;ll check out Twitterrific in say 6 months... For now I&#039;m using Osfoora which is even better (for me) than Twitterrific 2.  :)</description>
		<content:encoded><![CDATA[<p>I loved the old version (bought it)&#8230; I&#8217;ll check out Twitterrific in say 6 months&#8230; For now I&#8217;m using Osfoora which is even better (for me) than Twitterrific 2.  <img src='http://gedblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ged</title>
		<link>http://gedblog.com/2010/05/20/twitterrifics-tough-love/comment-page-1/#comment-34324</link>
		<dc:creator>Ged</dc:creator>
		<pubDate>Mon, 12 Jul 2010 13:42:07 +0000</pubDate>
		<guid isPermaLink="false">http://gedblog.com/?p=1813#comment-34324</guid>
		<description>Bigblue, we want shortcuts back as badly as you do and indeed the upcoming 3.0.1 takes some steps to make navigating around better including the ability to tap directly on links, usernames and tags from the timeline. Shortcuts are more tricky because of the nature of core text and the way the timeline is rendered.

We know its not as fast as it used to be, but the trade off in simplicity was worth it in our opinion for new users. Hang in there, thanks.</description>
		<content:encoded><![CDATA[<p>Bigblue, we want shortcuts back as badly as you do and indeed the upcoming 3.0.1 takes some steps to make navigating around better including the ability to tap directly on links, usernames and tags from the timeline. Shortcuts are more tricky because of the nature of core text and the way the timeline is rendered.</p>
<p>We know its not as fast as it used to be, but the trade off in simplicity was worth it in our opinion for new users. Hang in there, thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ged</title>
		<link>http://gedblog.com/2010/05/20/twitterrifics-tough-love/comment-page-1/#comment-34323</link>
		<dc:creator>Ged</dc:creator>
		<pubDate>Mon, 12 Jul 2010 13:39:14 +0000</pubDate>
		<guid isPermaLink="false">http://gedblog.com/?p=1813#comment-34323</guid>
		<description>Andrew, marking of tweets may return once we get the Mac version done and then add the ability to sync between versions. Until that happens, there is little point of having them. Marked tweets on one version don’t show up on another and this would simply frustrate users instead of help them.</description>
		<content:encoded><![CDATA[<p>Andrew, marking of tweets may return once we get the Mac version done and then add the ability to sync between versions. Until that happens, there is little point of having them. Marked tweets on one version don’t show up on another and this would simply frustrate users instead of help them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

