Building a buttonless WebKit thinclient device thingyyy

Luka Birsa, luka.birsa@visionect.si, @lukabirsa Founder, Visionect d.o.o.

Agenda

•  BrowserOS. •  WebKit. •  Building your own handheld device. •  Demo + Q&A

Why browser OS?

•  Lots of existing solutions. •  Lots of new web 3.14 stuff. •  Lots of people developers. •  Fastttttt development with cool tools.

…

Other reasons.

•  Layout engine. •  Yet another thing to learn. •  Why compile? •  Single point of failure.

Existing stuff.

•  Palm WebOS

Existing stuff.

•  Google ChromeOS

Don‘t reinvent the wheel, use existing stuff!

Use WebKit!

Pick your reason: •  Apple uses it, it has to be cool! •  Google uses it, it has to be cool! •  Try other solutions, see how badly they

suck.

WebKit FTW. Seriously.

A handheld eInk device??? WTF?

Why? (what about android, embedded linux, ebook readers)

A handheld eInk device??? WTF? •  Long autonomy. (y) •  Cheappppppppppppp. (not so much) •  Robust. (y) •  Universal. (y)

Wireless thin client.

•  Upgradeability. •  Processing power. •  Without WiFi, ZigBee, …?

(Are you mad?)

Building yourself a device.

It‘s simple! (not really)

Building yourself a device.

Design hardware. (cheap, easy, fast)

Building yourself a device.

Build hardware. (getting things, internals, externals)

Building yourself a device.

Create software. (reuse, reuse, reuse)

Building yourself a device.

PROFIT!!!!!! (if you‘re not too late)

Device demo.

It‘s working after 6 12 18 months.

Questions & Extra.

1. How to include your WebKit. (@Napsy (Luka Napotnik) @webcamplj.) 2. Looking for UX UI WD (call me ;) 3. Find me if you‘re thinking about your custom hardware.