Native apps became hugely popular for many good reasons - but many of those reasons are no longer valid. Performance, offline capabilities, push notifications, background workers, installation abilities, databases, and more have fundamentally changed browsers - and it's time to start using them. Together, we'll explore the current pros and cons of native versus web apps and take a deep dive into real world offline web app. By breaking down it's internals, we'll give an idea of what the web offers today and see just how awesome a truly offline web app can be.
Last active
April 10, 2016 23:50
-
-
Save deanmarano/3a53e34f1f856e2ac8e9e48bedc211fc to your computer and use it in GitHub Desktop.
Proposals
As citizens of the the web, we all have a right to know the state of our great language. Amendments are happening so frequently today's JS is hard to compare to that of our forefathers that generated this superb language. The new lingo that creeps in everyday - EMCA, ES2017, V8 - makes us sound like we're just babbling letters and numbers. As your speaker, I will make you a promise - I resolve to help improve our maps of the jargon, create a shared vocabulary, clarify who is making the decisions, and explore what will make Javascript great again.
How many ideas for side projects do you have? How many would you call completed? We are able to ship awesome projects for work, but the same is rarely true for personal projects. By taking the best practices in software development, and applying them to a side project, we can properly set expectations, but more importantly prove to ourselves that we can consistently accomplish great things. We'll journey through the struggles and successes of being on a one person agile team, and give you the tools to make real progress your own passion project.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment