Showing posts with label w3c. Show all posts
Showing posts with label w3c. Show all posts

Wednesday, 10 February 2010

O2 Litmus: Palm Pre Developer Event Part Two

This was the second O2 Litmus and Palm developer event in London. It was kind of hard to follow up on the first event at which all attendees got free Palm Pre’s, but they certainly did a good job. The food and beer was just as good as before and Dion and Ben know how to get developers on side.

First up was O2 with some updates on Litmus:

O2 Telefonica & Litmus

  • 7,000 customers now signed up for O2 Litmus
    • tech-savvy users willing to test new apps and provide ideas
    • To me this is the real strength of Litmus — it’s not just a developer program encouraging new apps. O2 are making use of the biggest advantage they have over a “dumb pipe” — their relationship with their customers
  • one shared mobile advertising org through whole of telefonica — starting to propose new advertising models:
    • click to call
    • click to receive an SMS
    • click to locate
    • receive an MMS with a map showing direction from where you are to the advertised location
  • developing O2 Priority Ticketing app
    • already available for iPhone
    • available on Palm in next 4-6 weeks through Litmus first
  • may open out ideas for developer community to build
    • especially around existing brands that don’t have a mobile presence
    • some private APIs may be available…

Palm Developer Evangelists

Ben Galbraith & Dion Almaer

  • app store growing fast (but linearly) since October, with slight acceleration
  • now up to 1,500 apps

Plug-in Developer Kit (PDK)

  • mechanism you can use to extend existing web environment — provides a plugin mechanism to the browser
  • will have a Flash plugin available to ship in Feb.
  • write code in C++ and have it available to the WebOS environment

Distribution

  • app data streams are available
  • visualisations appearing already:
    • Nicholas Felton — visualization guru
    • Project Appetite
      • allows you to send apps to the phone…
    • WebOS Schools
  • can get through app review in a couple of hours
    • that’s quick! where’s their team?
  • app catalog can act as intermediary, so can turn off a bad app
    • provides a quality source of apps
    • though you don’t have to go through the app store to make your app available

Editing — Project Ares

  • uses Mozilla Bespin (accent on the “e”), which Dion and Ben were involved with when they were working for Mozilla
  • enables you to drag and drop interfaces and build apps just using a browser

Incentives: Hot Apps Promotion

  • Most downloaded applications from Feb 1 to May 31
  • Separate pots for Free and Paid apps
    • Top 1: $100K
    • Top 20: $10K
    • Top 200: $1K
  • Will create a leaderboard in March
  • Can probably launch an app as late as April and still get a prize

European payment for app store

  • not here yet…
  • credit card to begin with
  • will follow up with operator billing, but can’t give any timings…
  • want to give as many options as possible to consumers
  • in-app purchases on roadmap too
  • app catalog releases may be restricted from their own purchase mechanisms to avoid confusion

Coding example

  • works a bit like rails
  • palm-generate -t hello.app <dir>
  • using palm-run wrapper script
  • can have multiple stages with multiple scenes
    • another stage might be notification stage
  • sources.json is where the first-assistant.js is loaded
  • prototype.js comes built-in
    • prototype can observe events and Mojo provides the touch events
  • can use standard media selectors to have different layouts per device
  • emulator is unable to play video
  • emulator always in charging battery mode
  • can see the source of all the Palm widgets
  • can turn on webkit inspector (palm-run -i) to dig in to any of the apps on the phone
  • although Mojo is the first attempt, you don’t have to use it — there are others… (pastrykit… :-) )

Q&A

  • push notifications?
    • Mojo messaging coming
    • provides unified mechanism for apps to work together to go to the network
    • saves battery life…
    • full multitasking with UI notifications
  • accelerated CSS transforms?
    • still coming soon…

Wednesday, 4 November 2009

O2 Litmus: Palm Pre Mobile Web Developer Event

Tonight was a really impressive event organised by O2 Litmus. The two guys from Palm did a very good job presenting WebOS and Palm’s plans for the future. The food and drink was excellent. And they even gave us a Palm Pre each to take home! Certainly makes me want to at least try out making an app.

As usual, here’s my notes for the evening in a vaguely coherent manner…

  • webkit appearing all over the place on mobile
  • as well as opera (there were a couple of people from Opera at the event)
  • HTML 5 is providing standardisation for web applications in the same way that HTML provided standardisation for web documents
  • web applications are escaping the browser:
  • why not flash, javafx or silverlight?
  • because:
  • “When you improve things by an order of magnitude, you haven't made something better — you've made something new” — Stephen Levy
  • Palm Pre uses V8 javascript engine, just like Chrome
  • WebWorkers provide background threads
    • came from Gears worker pool
    • invented to stop database access causing hangs
  • Chrome uses WebWorkers for extensions
  • Firefox hasn’t implemented SQLite, but may go for a JSON-based database, like CouchDB
  • CSS Transforms
  • “it’s not javascript people don’t like, it’s dealing with cross-browser issues”
    • anyone mention IE…?
  • “it’s not just going to be developing apps for Palm — it’s making things for the web”

some detail

  • Mojo Framework is open-source
  • Mojo uses prototype.js at the moment, but will be made nicer to use other alternatives later
  • dashboard items and popups are just DOM items
  • want to integrate apps into system — background apps

security

  • web browser provides normal web sandbox
  • applications get access to native services
  • certain APIs still need permissions granted
    • e.g. location
    • can get app to ask when API is used
  • would like to push local APIs to browser windows
  • apps are packaged and signed
    • working with developers to encrypt apps in different ways
    • would anticipate that developers would be able to opt-in to encrypt their app
    • protect against people uploading a copy of an app as their own
    • balanced against the benefit of view source on the web

app store

  • Palm would like a “web app store” to emerge
  • Palm doesn’t feel that it’s the right company to make this move
  • creating a Palm catalogue & developer program for mid-December
    • charging $50 for each app to be in the catalogue — as a spam filter
    • money goes to funding developing programme & catalogue service
    • interested in finding other “friction points”
  • can get an immediate acceptance into the web distribution of the Palm app catalogue
    • submit and get a URL straight away
    • can email/tweet other people
    • no review process
  • opening up the backend too — feeds of all the apps and charts
  • would like digg-style rating
  • a developer can choose to make an app available for specific markets
  • also aiming to provide metrics for developers, so they can see how users are choosing or not choosing their apps
  • payment:
    • right now they have PayPal
    • would like to support several options
    • want to decrease the friction

BONDI & others

  • palm works with them
  • including W3C widgets & geo
  • Palm way will be there originally, but will be switched out when
  • order depending on developer requests
  • native-accelerated CSS transforms are higher at the moment
  • “Palm pays us, but they didn’t pay us enough to sell out”

supporting open source

  • waiving cost for anyone working open source
  • $99 for developer

testing

  • O2 Litmus will be recruiting Palm Pre users for testing availability
  • DeviceAnywhere will feature Palm Pre in O2 VDL

feedback

  • devrel@palm.com
  • they already use Jira and want to open it something to the public soon
  • homebrew community will patch things before Palm do it themselves
  • there are differing viewpoints internally…

personal usage

  • like multi-tasking
  • don’t like UI latency
    • hardware is roughly equivalent to the iPhone 3GS
    • don’t have access to hardware GPU — so CSS Transforms is really important
    • will happen with a over-the-air software upgrade

multiple devices

  • Palm Pixi seems a lot nicer
  • different screen size (80 pixels shorter)
  • should design liquid layouts…
  • the future is devices in all kinds of form factors

tooling

  • there are tools for Flash — what about tools for WebGL, etc?
  • mozilla is making tools
  • e.g. Atlas from 280North
  • this week there may be something new released…
  • should flash be a native platform for apps on Palm Pre?
    • nearly supported for web pages — Adobe has shown something working already

Tuesday, 10 February 2009

MomoLondon: Mobile Web & Widgets

This was a great Mobile Monday London. Short, snappy presentations; an exciting and relevant topic with a real buzz going on; announcements that you heard here first; and really useful networking afterwards.

Many thanks to Dan, Alex, Jo & Helen!

GSMA One API

Kevin Smith — Vodafone

Kevin works closely with Dan Applequist.

Aim to produce network enabler APIs across mobile operators — charging, location, messaging, user profile, connection profile. They’re a network-level complement to OMTP BONDI, using a RESTful and lightweight web services system.

Major European & Asian operators all involved.

Have a reference implementation (beta) available at http://oneapi.aepona.com. Go try it out!

OMTP BONDI

Nick Allott — OMTP

I went to the OMTP BONDI codefest back in January (sorry, I ran out of time to blog about it). So I didn’t take many notes on this presentation.

OMTP is an organisation of mobile operators working together (who would have thought!), with manufacturers and system providers joining in the fun. They’re working on defining a javascript API through which a web runtime environment can access and interact with device-specific information.

So there’s a location API (compatible with the W3C spec as it goes), access to calendar and contacts, etc. Crucially, they’re actually building a reference implementation in order to figure out how the API should work. That way they can change their spec as they discover that it doesn’t quite work in real situations. The spec so far looks good — more details and the downloadable SDK at http://bondi.omtp.org.

The only problem is that the reference implementation is built on Pocket Internet Explorer. Great access to device information, but really hard to make a good-looking, functional widget using web standards…

They’ve got one demo widget so far:

  • EMCC Gig Guide w/last.fm
    • location
    • cached feeds
    • syncing calendars

And here’s where to find the latest widgets: http://bondi.omtp.org/widget-gallery/

Ikivo Enrich

Samuel Sweet, VP Sales

T-Omnia widget solution launched November 2008 in Korea. Based on Samsung, Windows Mobile & Ikivo Enrich.

  • SVG display engine (provided by Ikivo)
  • Javascript w/device APIs & AJAX support
  • Aiming to support HTML display engine later
  • W3C widget spec

“Putting lipstick on a pig” for Windows Mobile!

SK Telecom have had 300% increase in shipments month on month since they’ve launched the new interface.

Importantly, the W3C Widget spec now allows SVG as an alternate rendering option for widgets. This means that the Ikivo widget engine can be W3C-compatible.

Announcement tonight: Ikivo will be supporting BONDI

Firefox Mobile

Christian Sejersen

Currently called Fennec but will be called Firefox when it gets released. It runs on the same codebase.

Some countries currently have more than 50% Firefox usage. Mozilla are starting to wonder what they should do when they get a monopoly…

Fennec for Windows Mobile coming out soon (April?); Symbian version started not so long ago.

Shows a demo of running Fennec on Nokia N810 (Maemo) — Fennec Alpha Walkthrough on Vimeo

Browser controls are off the edge of the page to the left and right. Just scroll that way to see them.

Firefox Addons can be made compatible with Fennec. 20 or 30 Addons are available after a month, with no promotion from Mozilla.

There is full API compatibility between mobile and desktop, so once they add location & camera access to mobile, these APIs are available from the desktop build too.

My thoughts

As per Bruce Lawson’s talk at the Betavine birthday party, the browser writers don’t see the difference between mobile and desktop. I agree with them that the APIs and browser can be very similar, but I still think there’s a difference in how you would design a service.

A mobile service needs to take one particular function and “polish the hell out of it” (as goes the recommendation for iPhone app design). A desktop web app still needs to be polished, but has more leeway in its design. There’s also the interaction styles: a mouse is not a finger is not a d-pad, and you need to make the interface appropriate for each of these styles. Sure some of this can be done with stylesheets, but when you’ve got less screen space you want to deprioritise certain content off the screen completely.

Panel session

Chaired by Dan Appelquist

  • Francois Daoust (W3C)
  • Graham Thomas (T-Mobile)
    • 8 years at Nokia on UI & UX
    • Also bringing games into market (Club Nokia)
    • Been at T-Mobile for 7 years, now Head of Multimedia
    • T-Mobile very active in mobile internet — have iPhone and G1
  • Christian Sejersen (Mozilla)
  • Kevin Smith (Vodafone)
  • Brad Sipes (CTO, Ikivo)
  • Nick Allott (OMTP)

T-Mobile widget roadmap — want to have develop once, run across all handsets. Enabling the long tail…

SVG helps to bridge the gap between different screen sizes — since scalable. But Brad sees it more to “make things fun”.

Q: How does BONDI fit in with other web runtime initiatives, like Adobe AIR or Mozilla Prism?

  • CS: Prism currently in labs (local look & feel for web-based content). But don’t really have anything to say as Mozilla…
  • NA: OMTP did due diligence and found 25 different ways of doing the same thing. Operators decided on a common standard and then broke it in 25 different ways…
  • NA: 3 parts to standardisation
    1. APIs
    2. Display engine
    3. Security (one of the big problems for Java on mobile — see signed apps…)

Q: Sounds like lots of separate bits. Do they fit together?

  • NA: Yes. At least all the people on this panel do… OMTP working with W3C. SVG long-established as rendering tech. OMTP location API is W3C compatible, and could use One API as implementation by getting location from http query.

Q: How do I make money out of writing a widget?

  • GT: Key benefit of widgets — start using internet more, like iPhone & G1.
  • KS: Earn £20K from Voda competition…?
  • FD: sell the widget like the iPhone app store.

One advantage of interoperable widgets is that you can buy your widget from anywhere. You can have your own payment mechanism

  • DA: Can we build interoperable application stores? Micropayments never really went anywhere with the web. Will we get there with widgets?
  • FD: There were some standards about micropayments 10-15 years ago, but they werer never finished… Maybe it’s time to dust them off and complete them.

Q: What benefits do I get from a widget that I don’t get from HTML5? (Hugo from Google)

  • FD: Widgets give you more context, but it’s just a wrapper.
  • CS: A lot of the widget issues have come up because of security issues. But in essence it’s the same thing that needs to be solved across mobile and desktop.
  • BS: Widgets give you local application feel that HTML5 isn’t aiming for initially. But HTML5 will converge in the longer term.
  • NA: Some of the widget stuff has been created as a sticking plaster to avoid 15-20 different solutions while HTML5 gets itself ready.
  • DA: BONDI allows HTML5 over https to take advantage of secured APIs.

Q: My question: widgets on the standby screen? What about battery life?

  • GT: want them on the idle screen, with notification etc. Want eBay etc event-based dynamic.
  • CS: Palm Pre will be fully web-based
  • BS: T-Omnia has widget framework attached to button on the side of the phone. Can have lightweight widget framework on low-level phones that aren’t capable of running full HTML5 browser.
  • NA: battery notification & event APIs planned for BONDI 1.1

Q: What sort of security model?

  • NA: BONDI — consumer delegates trust to an entity. Doesn’t work to prompt the user for everything. Instead they should be able to trust Norton, Google, T-Mobile, etc.
  • DA: using XML digital certificates within the widget

Q: If you had one widget, what would it be and how would you interact?

  • BS: weather. would beep at me if thunderstorm coming in.
  • KS: widget that tells me if my 8 year old daughter has turned off her light…
  • CS: can I have a browser instead?
  • FD: tells me which way I should vote on W3C…
  • GT: M25 road traffic info
  • NA: a widget that syncs my contacts
  • DA: location-based ski conditions. What’s important is that the bar is lowered. I want my mom to write widgets!

Q: Have Palm come up with a way to make webapps feel like native apps? (Hugo, Google)

  • CS: Mozilla often have discussions about how to make the browser look native. But people don’t care. They want Facebook to look like Facebook, not a T-Mobile application.

Q: What do operators feel about making widgets more available? (David Stone)

  • GH: Shortly launching service with idle screen. Demo on idle screen. Gallery also available.

Saturday, 24 November 2007

BarCamp London: Don't Scrape, Glean (GRDDL) - Tom Morris

APIs break the principle of DRY — equivalent to “accessible version” of web sites…

W3C have defined GRDDL: defines well-structured process of converting XHTML (or HTML4 using Tidy) into RDF * works like a stylesheet on top of your HTML

can define with GRDDL how to get at data in APIs (incl. RSS & ATOM)

aim to make data layer separate from HTML but bound to it, just like CSS

XSLT templates provided to convert HTML into RDF using classes

using xsltproc > output.rdf to transform

  • have a template HTML page that includes links to xslt
    • either your own or standard ones
  • add a link to that page in the profile attribute of the head tag of the content page
    • can have space separated profiles
  • then go to triplr.org to convert page into RDF triples or JSON data

most languages have a sparql library to handle RDF pretty much like SQL

examples:

extends microformats — enables you to write your own