@briankardell
window
tabs
URL/Search
nav
bookmarks
menus
history
etc
"The Chrome" (app shell)
Safari (iOS/Mac)
Epiphany (Linux)
It's a big part of the stuff those are made of.
"Webkit-based"
JavaScript Core
A Primer for Busy People
Webkit
You can't run this.
Web Renderers
(WebViews)
Webkit
OS Implementations
A Primer for Busy People
This Part
Browser
"Chrome" & Internals
OS Implementations
Webkit
A Primer for Busy People
"Embedded Browser Web Renderer Thing"
Backend (Wayland/etc)
Webkit
Launcher (COG)
Not entirely accurate, but close enough for jazz...
Shared Investment.
Things you can build without IP or licensing issues
With an incredibly big pool of people
who can do the work
This work has a phenomenally a stable
'basic' codebase/core
(standards are forever*)
Easier integration with new and bigger ideas!
Online UI can be the same as embedded, it's decoupled:
There is a ton of content already available.
But embedded devices are typically
wildy underpowered compared to other uses.
Here's where it gets a little tricky...
Backend (Wayland/etc)
Webkit Port
A WPE Image for specific hardware
Launcher (COG)
> sudo something
These are not the things I had
questions about....
Web devs who are curious
Have a Pi
Comfortable
Building WPE/OS
Exceptionally small anecdotal survey...
Can I use?
First implementation in 2011
Landed in Webkit in 2019
Is it in WPE?
What does this mean to... uhm.... everything?
https://
Powerful features
Server?
Protocol?
Patterns?
What frameworks work better or worse?
Tips/architectures?
let the explore the space,
they will help.
Other successful things excel at this ...
They sell themselves.
is about the adjacent possible.
Boot up a device with content
Communicate with servers when you can
Potentially Update Content
Seems like this would be a common idea?
Also: Google proposal for
'the most basic problem'