I actually hate that apps are dumbed-down versions of websites!!!! why tf am I only allowed to draw freehand lines on Google Slides on a browser?
why is that missing from the app?? let me drawwwww
seen from Singapore

seen from Brazil

seen from India
seen from China

seen from Russia
seen from China
seen from United States

seen from United States
seen from China

seen from Netherlands
seen from United States

seen from United States
seen from Switzerland

seen from United States
seen from United States
seen from Saudi Arabia
seen from United Kingdom
seen from United Kingdom
seen from China
seen from Netherlands
I actually hate that apps are dumbed-down versions of websites!!!! why tf am I only allowed to draw freehand lines on Google Slides on a browser?
why is that missing from the app?? let me drawwwww

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch âą No registration required âą HD streaming
I would rather die, thanks.
"see more in the app" no fuck you show me on the website you asshole
Scan this QR code
open the app to sign in
add the authorizer app
enable 2fa
I hate the appification of the world
I loathe the modern nightmare of password requirements that make machine-password cracking infinitely easier than if they weren't in place
I want to go back to when the internet wasn't gated behind 5000 apps that all demand you have them installed to log in
Appification will control Marketing
Appification of Everything
[slideshare id=21696932&style=border:]
Below are a few links to new types of platforms that require application (software) development. The above set of slides are titled âthe APP-ification of the Webâ. Sure, we are witnessing the webâs explosion intoâŠ
View Post

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch âą No registration required âą HD streaming
Where do you Shop - App or Web?
There is a lot of buzz around "Appification" - how everything has an app/will have an app and hence "App Experiences" are so important. Trying to figure out how things will pan out in e-commerce/travel and similar categories. The broad ways in which we engage with content/services on the internet can be broadly categorized as : A. Transactional These are typically search-led. Lets say you want find the meaning of a word, read about how christmas is celebrated in another country, research what phone you want to purchase. You first search for what you need, judge which link is more likely to sever your need (often many of them), and consume the content. You are then done with the site, unless you find its content as something you are deeply interested in and would want to keep visiting regularly (in which case you might actually bookmark the site / subscribe to its feed / follow on twitter / install a companion app of sorts that site provides). B. Relationship based Relationship with a service/content provider is when you know where you want to go already, and it is a habit or ritual for you. Check Twitter, Flipboard, look at funny pics on Imgur, browse HN, facebook, check email, Google Reader, new apps on AppStore, etc. Its when either its a daily habit, or you already know that a particular activity will be done only at place X (you use a kindle, so buy books on amazon only...not going to search for the best place to buy it). So these are typically NOT search led. These could be lasting relationships or have limited shelf life. Games, for instance would be a relationship with perhaps a shorter timeline of expiry (sick of Draw Something in 1 weeks). Whereas, Facebook is something that is more lasting. Its obvious that category B is better suited to be apps - apps that one installs and keeps for a period of time. What about those that are partly search-led and partly relationship led? Categories where you have multiple relationships? Like say E-Commerce or Travel, where you trust a limited set of services, and know you can get a better experience in each of them individually through an app experience. Problem: You can't wholly commit to someone for these categories, despite better app experiences. Before I book a ticket from Chennai to Mumbai, I do check on multiple travel portals to see if I am getting the best price or offers for my flight tickets. I don't like the idea of installing apps of multiple travel portals and checking each of them one after the other. Its just not convenient. Neither am I comfortable enough to think "Oh! Let me just go with X. I hope they have the best offers!".  Which is why I end up  doing this on a laptop with multiple tabs open. How can this be solved better on a mobile? Answers? Maybe the answer lies in how our interaction with the devices are changing. Imagine if, instead of touch screens and looking at sites/apps one by one, we had the option of telling your phone (Siri like) "tell me the best prices and offers for flights from Chennai to Mumbai on 25th December. Check on Expedia, Yatra, Makemytrip.". And of course, complete the transaction through continuing in voice or through their app. 1. Do you face a similar problem? Do you shop/book tickets on mobile or PC web? 2. Does our future for these transactions lie in better designed app experiences or "getting the app out of the way" where we can?
The Appification Of Everything Will Transform The World's 360 Million Web Sites - Forbes
There is a seismic shift underway in the digital world that within a decade will completely transform the web into an App-o-verse. Several simultaneous trends are stacking up to change how we consume and create digital content, and platform companies are positioning themselves to enable the process.
What we are seeing are the early stages of what I call, âThe Appification of Everything.â This is not about adding more icons to your home screen, though, but about a fundamental shift in how we metabolize information and entertainment. The web as the universal storage medium is being superseded by the internet as universal flow medium. Instead of thinking about the web as a hierarchical tree of documentsâa Wikipedia of Wikipediasâwe need to start thinking about all of that content as an underlying service layer for application-based interfaces.
HTML5, le début de la désillusion ?
Facebook abandonne le HTML5 sur mobile et Microsoft transforme le HTML5 en application native sur Windows 8 âŠQuâarrive t-il Ă celui quâon donnait comme le grand vainqueur du Web toutes plateformes confondues ? Au dĂ©but le postulat de base Ă©tait simple : dĂ©velopper une application  en HTML 5 Ă©tait LA solution idĂ©ale, multiplateformes et universelle. Alors que celui-ci a pris ses marques sur le Web traditionnel, remplaçant progressivement les sites en Flash (doucement mais surement), dans le secteur du mobile la question fait toujours rage : « App ou HTML5 ? » . Ce dĂ©bat continue d'animer les discussions entre des milliers de spĂ©cialistes et n'a toujours pas de rĂ©ponse sure. JusquâĂ Â prĂ©sent on se concentrait surtout sur le nombre de tĂ©lĂ©chargements d'une application et de sa monĂ©tisation, laissant de cotĂ© les problĂšmes de performances. Et puis un matin, Facebook, le plus fervent dĂ©fenseur du HTML5 sur mobile, succombe au champ des sirĂšnes "natives" et  dĂ©cide dâabandonner les applications « hybrides » sur iPhone, iPad et bientĂŽt sur AndroĂŻd (hybride = coquille applicative mais contenu HTML5). En cause, des performances dĂ©plorables, et des temps de chargement spĂ©cialement longs, et au final, des utilisateurs mĂ©contents ! (Il nây avait quâĂ voir les notes (2/5) et commentaires sur lâAppStore pour comprendre l'ampleur du phĂ©nomĂšne). Un comble pour lâapplication mobile la plus utilisĂ©e au monde !
Ce changement de position de Facebook est un vĂ©ritable pavĂ© dans la mare du HTML5 ! J'avais dĂ©jĂ senti le vent tourner il y a quelques mois lors de lâannonce dâun SDK iOS natif (suite Ă lâannonce de lâintĂ©gration de Facebook dans iOS 6), câest maintenant chose faite ! Facebook veut finalement adresser de la meilleure façon possible chaque plateforme, et Ă date, il nây a pas de meilleure solution que de dĂ©velopper des applications natives en Objectif C, Cocoa ou Java, quitte Ă sacrifier le cotĂ© immĂ©diat des mises Ă jours dâune App HTML5⊠Â
Le pauvre standard qui Ă©tait dĂ©jĂ sur une mauvaise pente cotĂ© du hype nâest pas non plus Ă©pargnĂ© par la fragmentation des OS mais surtout celle des navigateurs. Ainsi mĂȘme si la plupart des browsers fixes ou mobiles gĂšrent correctement 80 Ă 90% des fonctionnalitĂ©s du HTML5 (feuilles de style/CSS3, Javascripts, canvas etcâŠ), les 10% qui restent sont un vĂ©ritable casse-tĂȘte chinois. Quelques poids lourds comme Internet Explorer jouent les troublions avec des scores de compatibilitĂ© trĂšs dĂ©cevants. Ainsi un site correctement codĂ© en HTML5 pourra trĂšs bien fonctionner sur Chrome qui est la Rolls en la matiĂšre, et trĂšs moyennement sur Internet Explorer qu'il soit 9, 10 ou Mobile ! Câest dâautant plus dommage que la « Web App » que vous allez pouvoir dĂ©ployer sans problĂšme sur le Chrome Web Store, le Facebook App Center ou tout simplement sur Tablette et Mobile via du Responsive Design (design dont le gabarit sâadapte automatiquement en fonction de la rĂ©solution de lâĂ©cran) ne fonctionnera pas de façon universelle sur tous les browsers ⊠On peut se demander quel est lâintĂ©rĂȘt de faire autant dâeffortâŠ
 Et ce nâest pas terminĂ© puisquâavec lâarrivĂ©e de Windows 8 et de son Ă©cosystĂšme « MĂ©tro » (NDLR : quâil ne faut plus appeler MĂ©tro...) Microsoft incite tous les dĂ©veloppeurs Ă crĂ©er de nouvelles applications dĂ©diĂ©es « Metro Style » pensĂ©es pour le tactile, dans un environnement Internet Explorer 10 qui ne brille pas en HTML5. Les dĂ©veloppements peuvent se faire en HTML5 « basique » (comprenez pas trop poussĂ©s) avant dâatterrir dans Visual Studio pour y greffer les composants de lâOS, un soupçon de Silverlight et finalement sortir une application quasi-native. Inutile cependant de croire que vous pourrez porter Ă lâidentique un site HTML 5 dĂ©jĂ existant (rien quâen terme dâergonomie). Prenons dâexemple du Financial Times qui a mis 8 mois Ă dĂ©velopper sa super WebApp http://app.ft.com,  on se dit quâils auraient pu proposer la mĂȘme expĂ©rience sur Windows 8, mais non, une App Windows 8 dĂ©diĂ©e est dĂ©jĂ disponible sur le Windows Store et elle nâa rien Ă voir avec lâoriginal (MĂ©tro Style obligatoire pour ĂȘtre rĂ©fĂ©rencĂ© dans le Windows Store). Je vous parie que Facebook est Ă©galement en train de plancher sur une application identique, entiĂšrement Ă la navigation horizontale avec des gros rectangles :) !
 Au final quâest ce qui est le plus intĂ©ressant pour un Ă©diteur ? DĂ©velopper sur les plateformes Ă succĂšs des applications natives certes plus couteuses mais plus performantes pour avoir des utilisateurs satisfaits et fidĂšles, ou alors essayer de dĂ©velopper une WebApp unique Ă budget moindre comme lâavait fait jusquâĂ prĂ©sent Facebook, mais avec des restrictions liĂ©es au hardware (puissance, accessibilitĂ© des pĂ©riphĂ©riquesâŠ) et au software (les browsers) ? La rĂ©ponse est loin dâĂȘtre simple mĂȘme si Ă court terme le chemin de lâapplication native semble ĂȘtre encore un peu plus ĂȘtre le seul viable. Mais dans lâĂ©tat actuel de mĂ©tamorphose du Web (cf mon article prĂ©cĂ©dent sur lâAppification) et lâarrivĂ©e de Windows 8, bien avisĂ© celui qui pourra prĂ©dire avec certitude Ă quoi ressemblera le Web dans 10 ans !Â