![]() ![]() 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. 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. 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. We’re still working on making improvements to the Teams feature and we’ll share more information about those updates as soon as possible.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. Video Docking allows you to watch a video while performing other functions like accessing content in the same column, and changing Decks.Create column types like profile, topics, explore, events, moments, and bookmarks. A Column Creator that offers a more intuitive way to create columns, and includes the ability to “Search Twitter” from within the column.Decks that let you organize your columns into groups for cleaner workspaces.Tweet order so you can view top Tweets or latest Tweets first in columns. ![]() Advanced search helps you find the content you're looking for.A Tweet composer that lets you create threads and add photos, videos, GIFs, polls, or emojis to your Tweets, including scheduled Tweets.You can also include existing columns from the standard TweetDeck version into your TweetDeck Preview experience. A sign-on flow that helps you set up your TweetDeck experience the way you’d like to. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |