Keynote day 2 - HTML5 DevCon 2013

Mozilla keynote day2
"the web is for everyone"
"everyone is a consumer and creator on the web"
HTML5 means browsers render html the same way...quite an improvement given the past

Phones are ubiquitous...the initial announcement for iPhone said no sdk, web only
 but the lashback happened and an sdk for native devs was added

Recent history is marked by the idea of built in obsolescence OR make style changes so that the owners feel out of date. This feeds the consumer culture. Leads to superficiality.
Web developers should not get into this game

Fragmentation is a given i.e. so many devices. You can't get it to work perfectly on all.

Few of you will be the really really successful guy but thats ok. Lets play the long game.
Don't fall into the too clever trap

We have an "awesome overload". Stop trying to impress each other. Instead build interesting things for the general populace.

So how do we disrupt?

Don't be concerned about the web. It will be there. But yes, it will be different in the future.
You will have a job in the future. You will have to stay on your toes but if you do so then ok.

Stop copying.

If you must Copy then kick arse e.g. fastbook

If you want to make money then do iPhone. But you should do more

Firefix OS
- a new free os
- everything is html5
- to replace old feature phones (not iphone/android)
- can search the web naturally, use an app and optionally download it
- access hardware apis view WebApi
- works with android

Context Aware App
- Christian wants to see more of these
- not just responsive layout BUT functionality appropriate
- functionality/behavior appropriate to the device e.g. phone vs desktop

Go Small, Go Offline
- cut down size
- allow people to work offline
- especially important for phones

Fix websites so that they work on Phones

Trust and Help the platformas
- if you see a bug, report it with screenshots and test cases

Don't animaate anything in javascript
- use css animations and transitions so they cna be accelerated by the browser


Comments

Post a Comment

Popular posts from this blog

My Reading Lists

I had some time over Christmas and decided to organize my reading lists. Interesting how some time away from daily work allows one to raise up your head   Uncle Bob on Principles of OOd See also book: Agile Principles, Patterns, and Practices in C# Available on Safari Books online. Algorithms in a Nutshell Nine   Algorithms   That Changed   the Future Programming Pearls book: http://www.cs.bell-labs.com/cm/cs/pearls/toc.html 97 Things Every Programmer Should Know Seven L a nguages http://pragprog.com/book/btlang/seven-languages-in-seven-weeks Codys book : http://www.domenlightenment.com/ Principles of OO programming: http://www.nczonline.net/blog/2012/12/18/now-available-principles-of-object-oriented-programming-in-javascript-beta/ Object Oriented programming with Stefan Stoy... Chrome V8 : http://code.google.com/p/v8/ https://developers.google.com/v8/ https://developers.google.com/v8/design - read this Mozilla Javascript page ...
Read more

angular js protractor e2e cheatsheet

Many from the protractor test suite category detailed task syntax example load page load a page browser.get('yoururl') browser btn actions browser back/forward browser.navigate().back() OR browser.navigate().forward() access elements on page See Protractor API list and examples from Protractors test suite access by angular ngmodel name (must match ngmodel in the html) this is the preferred approach element(by.model('person.name')); access by the css id on the page e.g, #user_name (but this can be brittle) element(by.id('user_name')) access angular binding to get generated value i.e. for {{}} element(by.binding('person.concatName')); access angular repeat list data (must match repeat stmt in the html) See Protractor test suit l...
Read more

react-select stacking order bug, z-index, layers and stacking

Image
Had to fix a tricky bug related to react-select recently (our Dropdown component wraps react-select). Here's the how the bug manifested. Dropdown does not overlay dynamically added content below it Variations of this have been reported since 2017. But I tried all the suggestions in the comments and none worked for me. I also tried wrapping the Dropdown in a div and changing z-index to be higher as well as making absolute position but no success. Changing the elements order in the html source and then reordering using flexbox order does work but it breaks the tabbing flow and is not recommended from an accessibility standpoint. One issue is the Dropdown is in a container and is constrained by the containers z-index. No matter how I change the Dropdowns z-index, its container is stacked below the next in stacking order. Google Chrome debugger layers tool provides a cool way to visualize layers. Could be better but helps, check it out below. You have to look closely but you can see h...
Read more