![add facebook to tweetdeck add facebook to tweetdeck](https://img.creativemark.co.uk/uploads/images/287/11287/largeImg.jpeg)
- #ADD FACEBOOK TO TWEETDECK INSTALL#
- #ADD FACEBOOK TO TWEETDECK PORTABLE#
- #ADD FACEBOOK TO TWEETDECK ANDROID#
- #ADD FACEBOOK TO TWEETDECK OFFLINE#
- #ADD FACEBOOK TO TWEETDECK WINDOWS#
![add facebook to tweetdeck add facebook to tweetdeck](http://assets.sbnation.com/assets/1020067/TweetDeck_lists_560.png)
#ADD FACEBOOK TO TWEETDECK INSTALL#
Install the TweetDeck by Twitter extension from the Chrome web store.Which was the point that Twitter were trying to make.Īnd because I can, using Google Chrome, I’ve pinned mine to my taskbar by doing the following: Īnd do you know what? It’s more or less exactly the same user experience.
#ADD FACEBOOK TO TWEETDECK WINDOWS#
It’s just that the standalone Windows version has been discontinued. Well, actually, it hasn’t gone completely. Twitter put a lot of effort into developing TweetDeck, removing support for Facebook and other social media platforms, and making sure it was the go-to app for both writing and consuming tweets. Twitter changed the rules around the use of its API, which made it harder for other clients to get a foothold, and then they bought TweetDeck to dominate the market. Occasionally I checked out other Twitter clients - Sobees, Seesmic, Twhirl, Spaz (yes, really!), and my favourite, MetroTwit - but I always returned to TweetDeck. It was probably my most-used application. I have used TweetDeck in one form or another since it was introduced in 2008.
#ADD FACEBOOK TO TWEETDECK OFFLINE#
This whole debate of web apps vs native apps came into sharp focus for me once again when Twitter’s native desktop app for Windows, TweetDeck, went offline on Friday 15 April. It was always much easier to find what I was looking for in the Google Play Store than while wandering around the world wide web. Quite the opposite in fact.Īnd as much as I argued for it, I didn’t do it either. My expectation was that we would slowly see a decline in native apps and an increase in people pinning web apps to their mobile home screens.īut… it never happened. applications that ran in the browser rather than either as a standalone native app or a native app wrapper for an embedded browser). And for a long time I argued in favour of web applications (i.e. I went into that session fairly neutral but came out a firm supporter of HTML5 web applications.
#ADD FACEBOOK TO TWEETDECK PORTABLE#
This approach, he argued would future proof our web applications, and as the performance of mobile devices improves, as well as the quality and speed of the software that runs on these devices, it would make more and more sense to be developing portable applications that could be used equally on desktop PCs, laptops, tablets and smartphones.
#ADD FACEBOOK TO TWEETDECK ANDROID#
Lauke passionately defending HTML5 applications, arguing eloquently that the web was the future and that we should be putting our efforts into developing write-once use-anywhere HTML5 web code instead of wasting time writing separate native applications for iOS and Android and whatever other mobile platform is flavour of the week. I don’t have an iPhone, and love my Opera Mobile browser on my Windows Mobile-based device, so no guesses on which side of the debate I sit on.Īt that meeting I remember then- Opera employee (and former web editor at the University of Salford) Patrick H. It was equally encouraging to hear the debate between device-specific apps (e.g. The mobile Web is something that is clearly going to grow and grow, and it was both encouraging and inspirational to see how universities are addressing it. This is what I blogged about it at the time: One of the workshops that I attended, that has genuinely stayed with me ever since, was one run by Mike Nolan from the Edgehill University called mobile apps vs mobile web. In 2010 I attended the Institutional Web Management Workshop ( IWMW) conference at the University of Sheffield. Let’s go back a few years… Using HTML5’s new flexbox capacitor we can instantly return to 2010 The past is a foreign country they do things differently there Perhaps the answer to the question of native vs web app is both. Perhaps, it doesn’t really matter whether the client runs natively under Android or iOS, Windows or Mac, what matters most is my data. But, ironically, it took until this past week, when my native desktop Twitter client stopped working, to realise that perhaps I’ve been missing the point all these years. As I write this, last week Twitter pulled the plug on TweetDeck for Windows, forcing PC users into their browsers to use the web version instead.įor at least the last six years I’ve been a vocal advocate of choosing web apps over native apps.