An open web for all


Published on

Keynote presentation at the how to

Published in: Technology, Design
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

An open web for all

  1. Chris&an Heilmann How to Web, Bucharest, Romania, November 2010 An open web for all
  2. I am Chris (@codepo8)
  3. I make technology easy.
  4. 6 Books, >120 slide decks, a few dozen videos, Blogger: Microsoft Scriptjunkie
  5. People come to me for advice how to get known on the web.
  6. Being a success on the web as a product depends on a few things.
  7. Having a creative idea. 1
  8. Finding people to build it. 2
  9. Getting found by people. 3
  10. What if I can tell you that none of these are a problem if you shift your focus?
  11. If you build for the web use the web to build.
  12. Be technology agnostic
  13. If you do all by yourself you will burn out quickly.
  14. Having a creative idea. 1
  15. I can’t help you with that - much.
  16. The main trick is to take the old and make the new by mixing and matching.
  17. A technique for producing ideas.
  18. This doesn’t even have to be creative! + =
  19. Please be creative - even when creating the $local Facebook is tempting to do!
  20. Finding people to build it. 2
  21. Good developers are hard to find.
  22. The main danger is that you make yourself dependent.
  23. Your product should not rely on one tech person.
  24. You should not tell your techies what to do.
  25. But you should tell them to document what they did.
  26. Separation of concerns should be high on your agenda.
  27. Data and interface are not the same thing.
  28. The interface will change and has to change - look at Twitter.
  29. There is one trick to make this work.
  30. Go and build an API!
  31. Reasons for APIs: You can change the backend or the frontend when you need to. You build them in parallel. You can have various different interfaces to the same content (mobile, web, iPad...) You give third parties access to your data and not to your system. You crowdsource innovation.
  32. Success stories?
  33. Using APIs is hard enough...
  34. Providing one should not be taken lightly.
  35. An API is for life, not just for the next press release.
  36. So instead of building your own infrastructure test the waters with an existing one.
  37. YQL
  38. YQL turns web services and data on the web into databases.
  39. YQL select {what} from {where} where {conditions}
  40. Let’s have a quick example.
  42. 2010/feb/11/winter-olympics-medals-by-country
  43. select * from csv where url=" key=tpWDkIZMZleQaREf493v1Jw&output= csv" and columns="Year,City,Sport,Discipline,Countr y,Event, Gender,Type" and Year="1924"
  45. You can store information in YQL and allow for writing to your API.
  46. All you need is a developer who knows how to access data on the web.
  47. YQL helps you filter and convert information - even for mobile environments.
  48. Using YQL has a lot of benefits: No time wasted reading API docs Using the console makes creating complex queries dead easy. Data filtering down to the least amount necessary. Fast pipes. Caching + converting Server-side JavaScript for complex conversions
  49. YQL can be your “try before you buy” offer
  50. And a real interface to play with is much more powerful than mockups and a lovely logo.
  51. Getting found by people. 3
  52. In order to get known in developer circles, release free stuff.
  53. This can start with adding your API to YQL as a new table.
  54. All you need to do is write an XML schema and put it on GitHub.
  56. But if I am open, won’t people steal my ideas and data?
  57. Yes, but not being open makes people creative in the wrong ways.
  58. Offering free things is a wonderful way to make people tell people about you.
  59. Your biggest fear should be being insignificant.
  60. There are a lot of tricks you can do - but that is for another time.
  61. Where to find more tricks?
  64. Christian Heilmann @codepo8 Cheers