data-driven web apps from the frontend. It‘s like jquery for data storage. And Hoodie is a bit special, because these apps are offline capable by default, meaning they won‘t break when the connection goes down, and this is basically why we‘re so interested in this whole topic. This isn‘t a talk about Hoodie, although it does come up a few times, it‘s about this idea of
going to be dense and fast, but also not technical. This one is about higher level things like Concepts, Interfaces, Experiences, and about understanding what the problem is in the first place. There are actually several talks today should be a lot more hands-on than this one. But before we get started, let‘s take a small detour and talk about building things.
Black Mountain College in North Carolina. Great thinkers and artists from all over the world wanted to remake education, make it holistic, give arts and sciences and crafts equal emphasis. One of the teachers there was…
in Montreal. The future was coming, and he wanted to build in a way that reflected this: new forms of living, new forms of community, new materials. And the dome had lots of advantages: it was sturdier, used less material, needed less energy to heat, and seemed like the structure of the future. Efficient, robust, highly aesthetic, and geometrically perfect. So why don‘t we all live in domes?
idea in general? We‘re in the future now, after all. Turns out what people really want is a building they can make their own, that is robust, adaptable, and flexible. Brick, wood and concrete boxes: simple, dependable, proven. Utterly traditional. You may despair at how conservative people and their choices are, but you'll have to admit that in the end, you'd rather have the thing that works, the thing that acknowledges how your actual reality is. Doesn‘t have to be perfect. You‘re not perfect either. And ironically, when the Black Mountain College had to expand its facilities, this is what they built:
windows to lean out of. Awnings to sit under, and walls to screw shelves into. They'd like to be able to put in a dividing wall or extend the building. They want to make good use of the space they have to build on. And it turns out that, paradoxically, the most conservative option turns out to be the most adaptable, the one most suited to everyday life. That box? Could be any number of things for any number of people. It‘s adaptable to everyday needs.
apps. Or native apps, for our purposes, it doesn't make a difference. But we make, and while we make, we imagine those things we make in their completed, working, usable state. We imagine them in the future, where all the cool people are using our stuff and making us rich and famous. But we‘re always saying: „In the near future, when this is ready, your life will improve a tiny bit“ And too often, our industry will communicate this like glossy science fiction:
startup, and like most pre-order/ crowdfunding companies, they have a vision, and they have a video. And it‘s basically a tiny slice of science fiction, a year or two from now: „here‘s how we imagine real human beings behaving in the near future“. And of course they show the tech and all, but it doesn‘t really matter what the product is, they all work by showing this evocative shiny, perfect and slick future. [plastc.com]
the future. They regularly release a so-called "Productivity Future Vision". Now, the name sounds as if someone just pulled three human resources buzzwords from a hat, but let‘s take a look at the current one:
screen! You‘re always connected, under water, in rural Cambodia, everywhere. The network is perfect, so your devices have no signal indicators. Your batteries are perfect, so your devices have no battery indicators either. But it feels… wrong. It's too smooth. It's not normal enough.
screen! You‘re always connected, under water, in rural Cambodia, everywhere. The network is perfect, so your devices have no signal indicators. Your batteries are perfect, so your devices have no battery indicators either. But it feels… wrong. It's too smooth. It's not normal enough.
It's too smooth. It's not normal enough. But it‘s the future! Every flat surface is a screen! You‘re always connected, under water, in rural Cambodia, everywhere. The network is perfect, so your devices have no signal indicators. Your batteries are perfect, so your devices have no battery indicators either. Source: https://www.youtube.com/watch?v=w-tFdreZB94
wi-fi with infinite bandwidth, no batteries run out, no traffic, no delays. —Tobias Revell Critical Design / Design Fiction All the systems in these videos are always flawless. „Everyone‘s happy…“, even old grandad with his wonky knee, because the humans may fail, but the systems always work. And by the way, you should absolutely look up Tobias Revells‘s work, it's eye-opening and very well done, which is why I'm stealing a bit more of it. Now, Google Glass used to be the future, now it‘s the past, but while it was still a thing, of course Google made a near-future sci fi video for it: [source: http://blog.tobiasrevell.com/2013/12/critical-design-design-fiction-lecture.html]
normal stuff like playing with dogs or a being late for a flight, but the basic symptoms are the same: the people, the lives, the circumstances: most of them are outliers, all very privileged people in a kind of post-scarcity scenario where, as Revell puts it, "it's a classic case of everyone suddenly being an ice sculptor and flying around in balloons". It's also not normal. And again: the systems are perfect where the humans aren‘t. It again assumes a perfect, global network, even in the sky, so it‘s still improbable, but has hints of normality. And now:
1969, with a vision of the 1990s. Same era as the Montral Dome from a minute ago. So I‘d just like you to picture that in your mind for a second. The future, seen from the 60‘s. You‘ve all seen the movies. Ok? Now consider that this was made by the British Post Office…
years into the future from Dollis Hill Research Station It seems rather normal. Why is that? Because it‘s not perfect. We see normal people at normal desks in an normal office. Also: the very first thing that happens: it doesn't work properly. The guy at the other end can‘t understand anything. And the weather's bad. Because it's London. It‘s normal. Listen: "suppose she makes an error". People don‘t make mistakes in Microsoft‘s future vision. Nobody has to ask glass to do something twice in the google thing. And the topics? Leases, bank statements, mortgages… normal normal normal. It's mundane, it's a bit wonky, but it's everyday life. What this shows is that thinking about the future is obviously a bit hard, because…
of the future lies not in designing the gloss, but in seeing beyond the gloss to the truths behind it. —Nick Foster The Future Mundane Source: http://www.core77.com/blog/columns/the_future_mundane_25678.asp
sci-fi: „here‘s how we imagine real human beings behaving in the near future“ But what I really mean, and what you really want, is „here‘s how we imagine something utterly normal happening in the near future“
as, and I'm sad to have to say this from up here, as well-educated, well paid people in the tech industry in a super-wealthy country, we're also not normal.
they usually bear little relationship to how and where our products will probably be used. We build from behind shiny new macs with full-sized keyboards in well-equipped offices with fast connections, but the target environments are radically diverse and different. And that‘s just us in our normal offices. The closer you get to San Francisco, the exponentially less normal things get.
could consume the web, it could also make it. That‘s no longer true for the majority of people. So you had to learn that people‘s devices were different than your dev machine, and now you realize that their circumstances are also very different, and require a bit of an empathic leap. Because their experience of the web is not only different to ours, it‘s also different to our historical experience of the web. Their first contact is radically different than ours was. But what counts for us, now, is that:
bus to work, you don't get the usual public transport experience. You've got free corporate wifi, air conditioning, leather seats… your commuting experience is far, far removed from that of basically everyone else. That‘s probably your baseline now. But in a way, we‘re all on the google bus. We‘re super privileged. And we frequently forget that we have to… [http://www.wired.com/2013/09/mapping-silicon-valleys-corporate-shuttle-problem/]
all the normal people it, that have average budgets and average resources, that world, from your perspective as a developer, is overwhelmingly mobile. Phones are mobile, tablets are mobile, this thing is mobile. This is a mobile device. Hundreds of thousands of people use these with 3G or LTE sticks. You might not, but they do. The big grey box is a relic. Mobile is normal.
Normality is imperfect. The web is very, very imperfect. The experience you're building? It's going to break for people. It's imperfect in ways you can't influence. You can write all the tests you want, but you can‘t fix 3G on the subway. And we do make attempts to import this reality into our work environments:
image, stating that „this is the internet now“. But that‘s not true. That‘s superficially what it looks like, on the surface, but what that is is a bunch of devices connected to a local dev server that‘s propably in the same room. But that iPad‘s never going on a plane, and that kindle will never be on the subway, and that game boy… doesn‘t matter. The point is not that you have to carry all those devices around in the world for testing, but rather that…
image, stating that „this is the internet now“. But that‘s not true. That‘s superficially what it looks like, on the surface, but what that is is a bunch of devices connected to a local dev server that‘s propably in the same room. But that iPad‘s never going on a plane, and that kindle will never be on the subway, and that game boy… doesn‘t matter. The point is not that you have to carry all those devices around in the world for testing, but rather that…
that go beyond your apps just breaking, becoming unresponsive, showing empty views, losing data, making people nervous with panicky error messages. You can now build your apps in ways that acknowledge the fact that the web is imperfect, that your connections to it are also imperfect, and you can provide good experiences regardless.
OFFLINE? - the app itself and its assets must be available offline. This is done through Appcache or Serviceworker, or through a native wrapper such as phonegap or electron. In a native app, this is a given.
WHAT NEEDS TO BE OFFLINE? more interestingly, the app must handle data in a way that doesn't require a connection. This is best done by reading and writing through a local data store which syncs, when possible, to the server. Let‘s see how hoodie handles this.
As far as this concept goes, feel free to replace localstorage with any in-browser storage of your choice. This, by itself, is enough for an app. You can wrap that in node-webkit and sell it to people who don‘t trust the cloud. But let‘s assume you want more, you want user management and syncing.
store [explain slide] We can do syncing because each user has their own little private database which only they can access. So it‘s very simple to decide what gets synced. It‘s the user‘s private data. Of course it should be on their machine, and we can easily keep people‘s data separate on the server.
Sync browser store So, how does it work? [Explain a direct message moving through the system] So we never have element talk directly to each other. They only leave each other messages and tasks, like passive aggressive roommates. It‘s all very loosely coupled and event-based. Which means that it can be interrupted at any stage without breaking. Messages and tasks will be delivered and acted upon whenever possible. It‘s designed for eventual consistency.
for lunch, BRB browser store The nice thing is: in most cases, the frontend doesn‘t care whether the backend is actually there or not. It will hang on to your data and sync whenever it can, and if your UI allows it, users can keep working without interruption.
Out for lunch, BRB browser store offline first apps are the web's honey badgers: they don't care, they just do their thing. Bees, tunnels, bad connectivity: the offline badger just keeps on going. It's how things should be on the internet: robust and fault-tolerant. Anyway, the point was:
Sync browser store If you want true offline capability, your app shouldn‘t try to talk to the server directly, only through sync. And you always want to keep a local copy in browser storage. That‘s really the central point: the user‘s data on the user‘s device, always. Sync is pretty hard. Really. You probably don‘t want to be implementing this yourself, there‘s just so much to get wrong. But whatever tech you choose to solve this with:
when you leave the world of timely, reliable communication, the local database, not the server’s, must be the gateway for all persistent changes in application state. — Aanand Prasad Offline Support is Valuable, and You Can’t Add it Later So then, the big question: [http://aanandprasad.com/articles/offline/]
Hoodie No magic, just a line of code. This is what using hoodie looks like. There‘s a hoodie object, with a store object, which has a couple of methods, like „add“. Add expects a type (todo) and an object with data in it.
Sign up a new user hoodie.account.signUp('[email protected]', 'secret'); // Listen for store events hoodie.store.on('add', handleNewObject) Using Hoodie Want to know when something changed so you can update the UI? Listen to events from the library
Sign up a new user hoodie.account.signUp('[email protected]', 'secret'); // Listen for store events hoodie.store.on('add', handleNewObject) Using Hoodie Wait, so how do I offline? 0_o So how do you make this work offine?
Sign up a new user hoodie.account.signUp('[email protected]', 'secret'); // Listen for store events hoodie.store.on('add', handleNewObject) Using Hoodie That‘s it. All you need to do is embrace a decoupled, event based architecture, which you probably do anyway. Talk to the api, let it sync for you, and listen to events from Hoodie to see if anything happened. And that‘s it. It‘s not a special feature you have to explicitly invoke, it‘s how the entire architecture works. You get offline for free. Let‘s just see that in action:
[2-B,1-A] DOC A [1-A] DOC A [3-C,2-B,1-A] DOC A [4-K,3-C,2-B,1-A] DOC A [[4-K,3-C,2-B,1-A],[4-D,3-C,2-B,1-A]] DOC A [[4-K,4-D],3-C,2-B,1-A] DOC A [4-K,4-D,3-C,2-B,1-A]
[3-C,2-B,1-A] DOC A [2-B,1-A] DOC A [1-A] DOC A [3-C,2-B,1-A] DOC A [4-K,3-C,2-B,1-A] DOC A [[4-K,3-C,2-B,1-A],[4-D,3-C,2-B,1-A]] DOC A [[4-K,4-D],3-C,2-B,1-A] DOC A [4-K,4-D,3-C,2-B,1-A]
[3-C,2-B,1-A] DOC A [2-B,1-A] DOC A [1-A] DOC A [3-C,2-B,1-A] DOC A [4-K,3-C,2-B,1-A] DOC A [[4-K,3-C,2-B,1-A],[4-D,3-C,2-B,1-A]] DOC A [[4-K,4-D],3-C,2-B,1-A] DOC A [4-K,4-D,3-C,2-B,1-A]
lot of the technical aspects, and now we were wondering: what does this mean? Which opportunities does this give us, exactly? Which problems can we now solve? And in my research I noticed I was suddenly reading articles from an area of computer sciences I really wasn‘t expecting. Because if you have several data stores with the same data in your system…
got a distributed system, for better or worse. And now a whole new range of interesting problems and opportunities arise. But before we even go there, we can look at some insights from the distributed systems world and see whether they can help us. And as we all know, there are only two hard problems in distributed systems:
The cost of knowing the „truth“ is prohibitively expensive A vendor is selling you a thing, but the vendor's system is not actually checking whether the item is actually present in the warehouse, or even if the warehouse still exists. It might be on fire, for all the web interface knows. But doing this check is prohibitively expensive and also quite challenging. There are other factors. Five other people may simultaneously buy something that is only in stock once. You could throw lots of money at engineering and try and make this perfect, and prevent four of those sales. But you're really pushing the limits of practicality. It is much more sensible to have your systems make educated guesses and assumptions, and make trade-offs on the few occasions when they're wrong. And then apologise to people, and recover from these edge cases and race conditions.
The cost of knowing the „truth“ is prohibitively expensive 2. There is no „now“ This is just physics. The parts of your system are not just distributed conceptually, there are actual physical distances between them, and there is latency between them. Your data realities can partition and end up on separate timelines that you have to merge again. And that means that…
The cost of knowing the „truth“ is prohibitively expensive 2. There is no „now“ 3. Failure is not only an option, it‘s an inevitability Warehouses catch fire. Connections go down. Networks partition. Hardware fails. The software is buggy. We can‘t know everything, we can‘t control everything. So how can we gain certainty about anything?
The cost of knowing the „truth“ is prohibitively expensive 2. There is no „now“ 3. Failure is not only an option, it‘s an inevitability Now Tyler here is urging us to stop trying to build perfect systems, but this is only half of our problem: You're building your app to be perfect, but at the same time, you're expecting the systems it runs on to be perfect, too. Just like in the Microsoft and Google videos assume a perfect world for their apps and services to run on. Anway, these three points aligned nicely with the problems people were having with offline scenarios:
spoke to lots of people about this. We were surprised at how many developers suddenly opened up about their offline troubles—realizing they’d had similar problems in the past, but never spoken to others about them, because it wasn‘t a thing. People had veeeery interesting and specific problems, ranging from building, and I quote, „runkeeper for fish“, for anglers in the norwegian wilderness, to several people trying to build super robust point-of-sale systems for places with bad connectivity. But we identified some central themes:
issue people seem to have is that they can‘t trust their apps to do the right thing when the connection gets dodgy. You can summarize this with the following user story:
that my data is actually available when I need it USER STORY And this is quite fundamental. It‘s so fundamental it probably gets forgotten most of the time. Of course users want this. But it used to be a painful problem, and it was easier to just fail, show errors and let people blame it on the telekom. But you can often do a lot better, and offline first is the way to go. But first, let me illustrate the problem:
book tickets and use their app under any circumstances, even when free soloing in the alps (remember, in the tech future, everyone is into extreme sports and ice carving)
who can‘t access his ticket, because the app won‘t start up when the connection is bad. It‘ll work in airplane mode, but on an actual high-speed train, where the connection is slow and intermittent, it fails, and it fails slowly. While the ticket inspector is breathing down your neck. A german ticket inspector. Bad user experience. The solution would be to store personal data and tickets locally, and not make the initial communication with the server blocking.
from a recent trip to Japan. Most of my photos are screenshots from where I was afraid that the data I‘d just fetched would vanish the next time I opened my phone. Because this kind of thing happens a lot:
took these screenshots, but then I made the mistake of, I don‘t know, switching apps or putting my phone away for a minute. And what happens? The apps ditch any data they may have had, then fail at loading new data, and then the user suddenly has no data at all. That‘s just not cool. So, we can use offline first to get…
apps are designed to only work while connected, even if there‘s absolutely no intrinsic requirement to do so. This is a relic from the age of the big grey box, of the terminal and the thin client, where all the computing power was probably far away from you. Now it‘s in your pocket, and we can do things differently.
yourself, why doesn‘t this just always work, online or offline? You should be able to add a meeting, mark a task as done, write a message, check in, post a picture… create stuff. Store now, sync later, but don‘t get in the way of getting things done if it isn‘t necessary. And again, this is an opportunity:
personal data on my device at all times USER STORY It is my personal data, why should it not be on here? I might need it, and you don‘t know when. Plus, in most syncing scenarios, I‘m the authority over my data, so just let me keep a local copy. Or rather, your server only gets to back up my data. Granted, this gets problematic if your app is highly collaborative, but if you have a use case where user data is fairly well isolated, you can easily do this. So, the potential benefit is:
more thing that frequently irked people when we talked to them about their offline woes: apps not being smart about what data they store locally. In short:
my needs in a sensible manner USER STORY Because I don‘t know in advance when I‘ll be offline. If I knew, it wouldn‘t be a problem, because I could prepare for it.
open them Nowadays you expect your podcast app for example to download new stuff as it appears, so it‘s there when you need it, without delay. And this is wonderful for offline, too. So think about whether your app could hang on to data, or even pre-fetch new data for your users before they need it. Similarly:
good in this regard. Fave something on the phone? It‘s now on the phone, always. And that‘s a good assumption to make on their part. You could take this further though…
can have offline maps, but you need to know that in advance. Get an offline maps app, or get google maps to cache your surroundings. But… maps knows where you live, right? Imagine if it would pre-emptively download your surroundings as soon as it notices you‘re on wifi in a different city than usual.
other hand, this nicely demonstrates some of the issues with caching local data: you need new UI elements, plus you need to answer some pressing questions: how long will the cached map be retained? Does it get flushed at some point? Can I remove it when I don‘t need it anymore? Can I cache more than one at a time, and if yes, is there some sort of limit? In short: how does it work and can I trust it? Or, for you as a developer: can you make it trustworthy while hiding all the complexity? Interesting questions, but a cool opportunity:
of new things you could be doing, and that these new things require new interfaces and in some parts even a new design language, because you have to communicate stuff to people you haven‘t had to communicate before
or not, you‘ll probably have to make this clear somehow. Threema does this by displaying an always-visible connectivity stripe at the top, red for disconnected, yellow for connecting and green for connected, and teaches you beforehand what the consequences of each are. Another big issue:
can be in? Stored locally, scheduled for sync, synced, possibly out of date, conflicting… possibly out of date is a state you‘ll get quite often in offline-capable apps, and you‘ll have to decide how crucial the age of data is, and how you communicate it. Because old data can still be useful while potentially being wrong. Think train schedules. Could be wrong, but communicate intent. And that‘s valuable.
There are loads of ways to solve this problem, depending on the use case, who you‘re developing for, and how crucial the data is to them. But one thing you‘ll probably have to do is
Not just whether they succeeded or not, but how and possibly why data has changed in their browser. This is probably one of the hardest UI problems related to sync, for example when it comes to chronologically sorted data, like chats or other streams/threads.
users only add data, why not always just let them do that and sync later? Well, it turns out that things aren‘t quite as simple, and that context really matters. Here‘s a fairly simple chat example that illustrates some of the things you‘ll have to keep in mind:
Meet on Thursday? A 10:03 - Sure, I‘m free. B 10:04 - Ah wait, meant Tuesday. A Now imagine that B‘s second message was written while one of the two was offline. On a train, in a tunnel or something.
Meet on Thursday? A 10:04 - Ah wait, meant Tuesday. A … Then the offline user reconnects and the messages sync up again. A receives B‘s missing offline message. So where do you put it? You can put it in the chronologically correct place, which makes sense in a thread context, because the order carries meaning. But that might mean the message appears somewhere out of the user‘s current view, way up there somewhere. That‘s a new UI challenge in itself. Or you could do what Imessage sometimes seems to do: display it in the flow according to the time it arrives at.
Meet on Thursday? A 10:04 - Ah wait, meant Tuesday. A … 10:05 - Hey A C Then the offline user reconnects and the messages sync up again. A receives B‘s missing offline message. So where do you put it? You can put it in the chronologically correct place, which makes sense in a thread context, because the order carries meaning. But that might mean the message appears somewhere out of the user‘s current view, way up there somewhere. That‘s a new UI challenge in itself. Or you could do what Imessage sometimes seems to do: display it in the flow according to the time it arrives at.
10:04 - Ah wait, meant Tuesday. A … 10:05 - Hey A C 10:06 - Hi C A Then the offline user reconnects and the messages sync up again. A receives B‘s missing offline message. So where do you put it? You can put it in the chronologically correct place, which makes sense in a thread context, because the order carries meaning. But that might mean the message appears somewhere out of the user‘s current view, way up there somewhere. That‘s a new UI challenge in itself. Or you could do what Imessage sometimes seems to do: display it in the flow according to the time it arrives at.
meant Tuesday. A … 10:05 - Hey A C 10:06 - Hi C A 10:07 - Hey, you free on Tuesday? A Then the offline user reconnects and the messages sync up again. A receives B‘s missing offline message. So where do you put it? You can put it in the chronologically correct place, which makes sense in a thread context, because the order carries meaning. But that might mean the message appears somewhere out of the user‘s current view, way up there somewhere. That‘s a new UI challenge in itself. Or you could do what Imessage sometimes seems to do: display it in the flow according to the time it arrives at.
Hey A C 10:06 - Hi C A 10:07 - Hey, you free on Tuesday? A 10:08 - Lemme see… C Then the offline user reconnects and the messages sync up again. A receives B‘s missing offline message. So where do you put it? You can put it in the chronologically correct place, which makes sense in a thread context, because the order carries meaning. But that might mean the message appears somewhere out of the user‘s current view, way up there somewhere. That‘s a new UI challenge in itself. Or you could do what Imessage sometimes seems to do: display it in the flow according to the time it arrives at.
A C 10:06 - Hi C A 10:07 - Hey, you free on Tuesday? A 10:08 - Lemme see… C 10:09 - I asked B too, btw A Then the offline user reconnects and the messages sync up again. A receives B‘s missing offline message. So where do you put it? You can put it in the chronologically correct place, which makes sense in a thread context, because the order carries meaning. But that might mean the message appears somewhere out of the user‘s current view, way up there somewhere. That‘s a new UI challenge in itself. Or you could do what Imessage sometimes seems to do: display it in the flow according to the time it arrives at.
Meet on Thursday? A 10:03 - Sure, I‘m free. B 10:04 - Ah wait, meant Tuesday. A This guarantees that the message will actually be seen by A, but this approach has the potential to change meaning, because message order is meaningful. And this is only text-based, one-dimensional data. A simple chat, one of the simplest examples I could think of. What to do with deleted items, things that can’t be organised in lists, objects that aren’t in themselves immutable? There‘s a lot of potential for complexity here, so that‘s something to be aware of.
Meet on Thursday? A 10:03 - Sure, I‘m free. B 10:04 - Ah wait, meant Tuesday. A This guarantees that the message will actually be seen by A, but this approach has the potential to change meaning, because message order is meaningful. And this is only text-based, one-dimensional data. A simple chat, one of the simplest examples I could think of. What to do with deleted items, things that can’t be organised in lists, objects that aren’t in themselves immutable? There‘s a lot of potential for complexity here, so that‘s something to be aware of.
and capable. Here‘s a photo editor. It‘s not photoshop, nor is it trying to be: it‘s quick, easy, no installation, cross-platform, auto-updates, and does most of the things you want in a simple photo editor. You‘d probably want it to work offline, though.
and drumkits and audio, and it runs in the browser. This is part of a masters thesis by Jan Monschke, and it‘s really bleeding edge, but just imagine where this tech will be in a year. Cross-platform garage band? That‘s pretty damn cool. But again, it can‘t be used offline, and that‘s a disadvantage in comparison to the native apps it competes with. But aside from competing with native apps, what are the…
me. This is the way to the snappiest experience. The data may be old, but at least it‘s there. And in many cases, time isn‘t doesn‘t even invalidate the data, so there‘s still a benefit to having it.
capability protects from service interruptions. Interestingly, we hadn‘t even anticipated this. We have a fairly large service running on Hoodie and had to briefly take it down for maintenance, and most people using the app at that very moment didn‘t notice. Turns out: It doesn‘t matter if your app can‘t reach the server because the user is on the subway, or because the server is down. It‘ll still work.
CARE • Better experiences OFFLINE-FIRST ADVANTAGES Better experiences. Apps don‘t lose data. Apps are more trustworthy. Apps are more usable and useful. Apps cause less frustration.
CARE • Better experiences SAVE ALL THE TIME OFFLINE-FIRST ADVANTAGES And remember, you‘re saving to a local store first. You can save after every single keystroke if you want, and sync to the server every couple of seconds. Forget save buttons altogether. There‘s a lot to be gained from an offline-first architecture that‘s not completely obvious at first glance. Anyway:
Image manipulation, maturing web audio APIs, and there‘s a lot more to come. At JSConf EU last year, there was a lot about ServiceWorker, client side storage and web crypto: all just coming in to existence then, cutting edge, but wildly promising. And now?
be written in JavaScript. —Jeff Atwood „Atwood‘s Law“ And if it‘s in the browser it‘s going to be used in a mobile context, and it‘s going to be offline at some point. And it‘s not just about increased mobility any more:
awesome interactive document viewer into being the world’s most advanced, widely- distributed application runtime. —Tom Dale Progressive Enhancement is Dead The web is very attractive platform for developers for many reasons, and as web apps gain complexity and mobile native app usage increases further, users will simply expect a mature and solid experience. Waiting for more cell towers to be built won‘t help them. Your apps have to work regardless of the circumstances. Here‘s the conclusion: Source: http://tomdale.net/2013/09/progressive-enhancement-is-dead/
that works completely offline, it has offline maps, and it can even take photos while offline and store them until you‘re back online. It runs well on my dodgy, nearly 4 year old android phone. It‘s only going to get easier, faster and more stable from here on out.
espylaub
mackee
niftycorp
kimura_m_29
tucksaun
myohei
seyfoyun
92thunder
sugi_0000
xosofox
shibuyamizuho
orgachem
kwakeuijin
csswizardry
kneath
garrettdimon
addyosmani
andyhume
kevinliebholz
jcasabona
shlominoach
ufuk
gr2m
eileencodes
michaelherold
![[…] for every miraculous iPad there are countless partly broken](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_19.jpg){kind=link}
![FRONTEND App hoodie.store browser store BACKEND Hoodie Sync [explain slide]](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_44.jpg){kind=link}
![{ "key": "value", "number": 1, "numbers": [2, 3, 4, 5],](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_58.jpg){kind=link}
![{ "_id": "value", "_rev": "1-F00B44476123…", "numbers": [2, 3, 4, 5],](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_59.jpg){kind=link}
![{ "name": "Alan Turing", "birthday": [1912, 07, 23], "hero": true,](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_60.jpg){kind=link}
![A B DOC A [1-A]](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_65.jpg){kind=link}
![A B DOC A [2-B,1-A] DOC A [1-A]](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_66.jpg){kind=link}
![A B DOC A [3-C,2-B,1-A] DOC A [2-B,1-A] DOC A](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_67.jpg){kind=link}
![A B DOC A [3-C,2-B,1-A] DOC A [2-B,1-A] DOC A](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_68.jpg){kind=link}
![A B DOC A [4-D,3-C,2-B,1-A] DOC A [3-C,2-B,1-A] DOC A](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_69.jpg){kind=link}
![A B DOC A [4-D,3-C,2-B,1-A] DOC A [3-C,2-B,1-A] DOC A](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_70.jpg){kind=link}
![A B DOC A [4-D,3-C,2-B,1-A] DOC A [3-C,2-B,1-A] DOC A](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_71.jpg){kind=link}
![A B DOC A [4-D,3-C,2-B,1-A] DOC A [3-C,2-B,1-A] DOC A](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_72.jpg){kind=link}
![A B DOC A [4-D,3-C,2-B,1-A] DOC A [3-C,2-B,1-A] DOC A](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_73.jpg){kind=link}
![A B DOC A [4-D,3-C,2-B,1-A] DOC A [3-C,2-B,1-A] DOC A](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_74.jpg){kind=link}
![DOC A [5-L,4-K,4-D,3-C,2-B,1-A] A B DOC A [4-D,3-C,2-B,1-A] DOC A](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_75.jpg){kind=link}
![DOC A [5-L,4-K,4-D,3-C,2-B,1-A] A B DOC A [4-D,3-C,2-B,1-A] DOC A](https://files.speakerdeck.com/presentations/15b8de87b09d4c13ba6e3b64708ff6bd/slide_76.jpg){kind=link}
