Showing posts with label html5. Show all posts
Showing posts with label html5. Show all posts

Tuesday, 16 July 2013

MomoLondon: Operating Systems – a new set of Davids take on the incumbent Goliaths

Some really useful insights this week — with the panel providing a different perspective on the mobile industry than the usual. Although one question started on the HTML vs Native war, this was quickly knocked on the head and left for a future Mobile Monday.

I really get the FirefoxOS aim of making the web more accessible to new markets around the world. Mozilla has its own motivations for making a new OS, which are different to the usual “make as much money as possible”. It will be very interesting to see how they compete against the low-cost Android devices that are getting cheaper every year.

As for Ubuntu Phone & Tablet, this seems to be more about an operator story than a consumer one. I’m not sure of the reasons why a developer or a consumer would choose an Ubuntu phone. Having played with the sample tablets that were available on the night, I couldn’t see any particular advantages over Android or iOS (or Blackberry or Windows for that matter).

Ubuntu’s message seems to be that operators can customise the devices for their own content (that always goes down well with consumers, not!), or that you can have a single superphone that you can plug in to a screen and get a desktop experience (seems like a bit of a gimmick to me…).

Thanks to Geoff Blaber for being an excellent chair and keeping the discussion moving fluidly, and to all the panel members and organisers for a great evening.

Intro

Victor Palau, VP of Phone & Hyperscale Delivery at Canonical

  • hardware & os market has become monopolized in last few years
  • standardization on Linux kernel (mainly from Android) makes it much quicker to set up a new operating system
    • don’t have to worry about chipsets etc as much as in Symbian days
  • but platforms have to have something

Developer Economics Q3 2013

Andreas Constantinou, MD at Vision Mobile

  • launching latest research today
  • Ed.: this is always a really good read — Andreas gave us some highlights, but go and download the full report at http://www.developereconomics.com/go
  • html5 is number 3 development platform in use
    • Android leads, then iOS, everything else way behind
  • 61% of html is direct to browser
    • then phonegap at 27%
  • Windows Phone going down in intent share (i.e. less developers interested…)
  • iOS still leading monthly revenue at $5,200
    • Android catching up at $4,700 (using in-app advertising as main booster)
    • revenue models differ by platform
  • seeing an increase in platforms used by individual developers
  • main platform almost even between Android (34.4%) and iOS (32.7%)
    • html5 behind at 17.5%
  • report trying to quantify platform loyalty amongst devs
  • also trying to show which platforms are best for different challenges
    • and the different motivations for different developers
  • more experienced developers are using more tools
    • e.g. crash reporting, ad networks, push notifications

Panel

  • Geoff Blaber @geoffblaber
    • CCS Insight research house
  • Alex Sinclair, CTO of GSMA
  • David Wood @dw
    • principal at Delta Wisdom, formerly prime mover behind Symbian
  • Andreas Constantinou @andreascon
    • MD at Vision Mobile
  • Victor Palau @victorpalau
    • VP of Phone & Hyperscale Delivery at Canonical
  • Christian Heilman @codepo8
    • Principal Developer Evangelist (HTML5/Open Web) at Mozilla

What do new platforms offer manufacturers?

  • GB: essentially just 2 OEMs (Apple, Samsung) making any profit
  • CH: not a problem of distribution but where it is going
    • producing lots of phones in saturated market
    • Mozilla’s job is to keep the web open
    • the web is worldwide
    • FirefoxOS is targeting markets that mostly have featurephones, aiming to be people’s first smartphone
    • you can get old Androids but they’re 4 generations behind with old browsers that don’t show stuff right
    • manufacturers actually quite interested in this proposition
    • Foxconn hiring 3,000 people to make a FirefoxOS tablet
    • Samsung & Apple neutering open web — you need expensive hardware and a credit card to be a part of it
    • in Spain selling €79 phone with €30 pre-paid credit
  • GB: open initiatives have failed in the past: WAC, etc
  • VP: open initiatives can have trouble with leadership
    • Canonical remain open but have strong leadership
    • offering operators ability to showcase their content
  • DW: two good cases for disruption
    • companies that have shown their staying power
    • just an improvement in battery life would be welcomed…
    • smartphones naturally get stretched as new environments come along — and leave space for niches

What about the ecosystem?

  • AC: for any platform to be successful need buy in from:
    • developers, operators, manufacturers, users, …
    • devs have to learn new platform
    • users don’t care what’s underneath
    • operators have pre-allocated slots, often by OS
  • CH: Windows Phone is a great example
    • not seen the depth of commitment required from the operators
    • not willing to take the risk
  • AS: not all operators subsidise handsets
    • when a new version of the iPhone comes out, AT&T’s share price drops as they have to subsidise it
    • need an alternative
    • different operators placing different bets
  • AS: operators want to get their content onto devices
    • but are struggling to do so with iOS & Android
  • Ed.: this is probably one reason why those two are doing so well!
  • CH: app discovery as easy as searching
    • search for a movie: get IMDB deep link
    • go back to search and long-press to install app
    • then get offline goodness etc
    • drives me crazy that I have to wait 5 months for a game my friend is playing on his different device

What about the corporate sector or 3rd sector (training & education)?

  • VP: one of our main focuses at Ubuntu
    • have a very secure platform, bringing to phone
    • converged device — plug in your phone and get full desktop
    • good for enterprise: single device, secure
  • CH: enterprise difficult to get into as wedded to Blackberry or other platform that’s integrated with email system
    • difficult sell for open source
    • 3rd sector is an easier sell
    • e.g. simplified phone for elderly: just photos of family — click to call
  • AC: changing the UI of the phone reminded me of SavaJe (way back in 2006, bought and swallowed by Sun)
    • html5 is top platform for enterprise
    • top driver is efficiency
  • CH: developer scarcity — don’t have to go out to an agency
    • just use existing web team
  • DW: enterprise can drive home usage too
    • LinkedIn most popular enterprise app?
      • switched back to native on mobile as tools were not good enough
  • AC: html5 apps are like a car without a break
    • once it starts leaking, you can’t stop it

Are you seeing apps migrating from mobile to desktop?

  • DW: more about device usage — consumer behaviour is leading
  • VP: end of Windows XP support is great: making people think about it
    • at the moment can’t replace them with an html5 app
    • but solutions available in Ubuntu
  • AC: crawled the Google store to find APIs used
    • only 1 in 4 Android apps could be done on straight web
  • CH: that’s why Firefox provides access to device
    • some memory leaks come from platforms they are using to generate code
    • Chrome and Firefox dev tools making great strides

How many years are going to pass before clients say “don’t do native”?

  • VP: has to be lots more about what’s good for consumer
    • depends on the situation and who you’re aiming it at
  • AC: it’s not an either or…

Privacy: number one for Mozilla / chinese walls between work & home

  • AS: virtualisation of phones available: multiple phones in one
    • lots of companies don’t use Dropbox for security reasons
    • don’t think about all the data that certain closed OSes are capturing about us
  • DW: trustworthy and transparency may be change reasons
  • CH: already seeing that for Firefox browser
    • sometimes have to make the UX harder to make people think about what they are doing
  • VP: full Linux implementation
  • GB: isn’t there an argument that deep integration with Google is part of Android’s success?
  • AC: people don’t ask if Facebook & Google are spying on them: they give you something back which you perceive to be of value
  • CH: it’s actually more addiction than value…

What positive reasons for getting new platforms?

  • AS: it comes down to competition
    • is it a good idea for just a few companies to make the profits?
    • I represent people who used to make the profits from the industry…
    • was previously director of WAC, but by the time it was ready there was no need for it as only two platforms to develop for
    • operators want to implement RCS/joyn (operator-based IP messaging, voice, video, etc) and new platforms give them the chance to get involved
  • DW: so many variations
    • e.g. Nokia mega pixel camera: “average user only cares 16/23 about camera pixels” — but actually there’s a reasonable niche here

What about the important services that users expect?

  • e.g. Skype, Google Maps
  • AS: was in Korea last week: their search provider is being investigated for monopolistic practices
    • also a messaging provider was worried about operators implementing RCS/joyn and taking away their revenue stream
  • CH: service in China to add “written on an iPad” to the bottom of your email
    • $5 a month, and they stole your email data!

What about individual permissions?

  • CH: permissions can be asked on a more granular basis
    • no great list of permissions as for Android
  • AC: how much would you be willing to pay for a service that monitored and reported how your private data was being used?
    • people want it but are not willing to pay for it

Who is likely to nudge sub-saharan Africa into smartphones

  • full of featurephones
  • OLPC not doing that well
  • CH: OLPC didn’t do so well as missing network connectivity
    • Ushahidi is building a wireless BRCK to be a modem for Africa
    • if someone asks “what if Google or Apple go after these markets after you”, answer is “then we’ve won!”

Visiting from Momolo Nigeria: what difference will a billion users in Africa have on design considerations?

  • 120million mobile phones, mainly featurephones
  • CH: sent UX designers to South America to come up with use cases
    • build apps with Telefonica targeted at those markets
    • need to meet somebody local who knows the area
    • can’t assume that everybody wants the same thing
  • VP: community is very important
    • a lot of people in Africa want to contribute and make things better for their community
    • have a whole set of local community councils
    • e.g. large Catalonian community
  • AC: if you need to access the internet you need a data plan
    • developing countries have very expensive access plans
    • need to have smarter ways of micro-access to the internet
  • DW: designing meaningful UI for people who can’t read or write
  • AS: some operators already doing micro data plans
    • e.g. facebook access not coming out of data plan (facebook zero)

Closing remarks

  • GB: often on West Coast of US, it’s Android, iOS or the highway
    • been impressed that there’s a great strength in the alternatives
    • barriers to entry getting lower
    • html5 provides common access
    • market driven by growing diversity
    • fragmentation in OS space is likely to proliferate
  • AC: there is no black or white
    • there’s always multiple alternatives
  • AS: there’s a definite need & opportunity
    • don’t know who is going to win
  • DW: which David will survive?
    • execution: can the company keep pushing out high quality?
    • proposition: will people bit?
    • community: can they start a virtuous cycle?
  • VP: can you get a consumer to buy something different?
  • CH: there’ll be a lot of opportunity for a lot of players
    • we were the only cool thing in MWC twice in one day
    • device should not spy on you: built the internet in a different idea and this should exist on mobile phones too

Announcements

Thursday, 24 January 2013

MomoLondon: Demo Night 2013

Another fun demo night from Mobile Monday London. Some new ideas and some old — you never know which ones are going to stick!

My bets are on Vyclone and Critical Arc…

Blue Badge Style

Fiona Jarvis & Kishan Gupta @bluebadgestyle

  • a guide for the discerning less able
  • app available for iOS: Blue Badge Style
  • graduated from the Mobile Monday & UCL Mobile Academy
    • (it’s really great! sign up now! :-))
  • social media advisor suggested:
    • video of app to attract people to download
    • RSS feed in app
  • added TTS (but not voiceover?)
  • got 1000 downloads in Nov (PR & press) + 300/month afterwards

Boss Level - Scavengers

Nick Brown @boss_level

http://playscavengers.com

  • game based solely in HTML5
  • aimed at PC, mobiles, tablets & smart TVs
  • want same control system across everything
    • up down left right & select - lowest common denominator
    • fixed 720x720 resolution at the moment (will need to change for different devices)
  • closed alpha at the moment
  • aiming for Kickstarter to raise profile
  • cross between xcom & worms
  • freemium business model with in-game purchases
  • also thinking about a store for game assets
    • there’s a game editor that allows you to completely customise levels and characters
  • would rather not have in-game adverts, but depends on the eyeballs
  • currently two developers

Connecthings

http://www.connecthings.com/

  • NFC tags for street furniture
  • 1500 tags displayed in Strasbourg
  • real-time transport info
  • integrated with cycle info too
  • also has event & POI database
  • POI tags show POI info first, transport tags show transport info first
  • tags have QR codes too
  • license the platform to municipalities
    • though not sure how well it would go down with councils that already have their own portals….

Critical Arc

http://www.criticalarc.com/

  • previous company led security & surveillance for Olympics
  • security & safety in large open spaces
    • e.g. universities
  • define SafeZones where there is a response team available
  • security team have an app to see a situational view of the campus
  • free app to call for help & get notified
  • have created a platform for sharing location and situational information
  • universities are first market
  • no tracking in the background for general public
  • security officers are tracked in the background
  • Wi-Fi positioning covers off GPS issues
  • can report on security staff location — heatmaps etc, can be used to actively plan response

Decibel Analytics

http://www.decibeltechnology.com/analytics/ @decibelanalytic

  • actionable analytics
  • object maps, which integrate with elements on page, to show which are actually being clicked
  • attention maps — shows which areas of page are actually viewed
    • i.e. where is the fold for all your customers…?
  • which content is contributing most to goals & revenue generation
  • can filter by device and by incoming source
  • adding A/B testing soon

Men’s Fitness UK iPad app

Paul Cooper, Design Director, Dennis Publishing @dmfcoops

iPad app: Men’s Fitness UK

  • COPE — create once, publish everywhere
  • Drupal CMS with responsive design & native elements
  • started with The Week (iPhone & iPad)
    • takes one person one day to lay out
    • less than 100Mb an issue
  • now done a monthly magazine — more content
  • Drupal 7 & responsive is a complex thing
  • Adobe DPS takes over a week to lay out an issue of EVO
  • content producers (photogs etc) struggled a little with responsive design, but get training
  • can preview the issue before generating the app
  • looking at licensing the system to other parties
  • developing a system like InDesign that outputs responsive HTML

GO!Enterprise

Globo plc - Enterprise Mobility in a BYOD world

http://goenterpriseserver.com

  • deploy access to back office systems in a secure manner
  • no need for mobile device managment
  • client app available from standard app stores
  • three products:
    • office — point and go
    • mobilizer — development for custom enterprise apps (cross-platform)
    • reach — make apps for customers

Trademob - mobile click fraud protection

Adrienne Gauldie @adriennegauldie (ag@trademob.com)

http://www.trademob.com/

  • did a study in june (6m clicks)
    • 22% accidental (< 0.1%)
    • 10% botnet & hijacked clients
    • 8% server-side fraud
  • can see it from data…
    • e.g. in-app clicks from non-mobile user agents
  • don’t get fraudulent clicks from publishers with real customers
  • building a blacklist of dodgy publishers
  • 100 people in company

Vyclone

http://vyclone.com/ @vyclone

Download the app for iPhone

  • wouldn’t it be amazing if we could make a single video from all the angles at a rock concert…?
  • combine multiple vids in one
    • had 200 people filming a Jason Mraz concert
    • 150 people at Ed Sheeran in Hammersmith Apollo
  • business model:
    • lots of interest from music industry
    • want to get footage and release it to fans for behind the scenes
  • copyright: music industry recognise that this is already happening
    • now they get access to video, so a win-win
    • customers can choose to keep video private, or share with everyone
  • app is winning lots of awards!

AudioSnaps

Marc Sallent, We Choose Fun

http://audiosnaps.com

  • record 5 secs of ambient sound while taking a picture
  • JPEG + MP3 = JPEG! (plus extensions)
    • all devices can still show it
    • web site can play audio with just one line of javascript
  • why not just take a short video?
    • want to capture a moment, not tell a story

Chirp

Geraint, Animal Systems

http://chirp.io

Download the app for iPhone

  • send small amounts of data using sound
  • want to release an API for third parties
  • have an arduino that can chirp
  • teach the machines to sing!

Catch-up with last year’s demos

Two of last year’s Demo Night presenters returned to give us an update. See my notes from last year.

Ko-Su

http://ko-su.com @kosumobile

mobile learning for everyone

  • demoed last year, one month pre-release
  • been accepted into BBC Worldwide Labs
  • material created in lots of countries around the world
  • now “officially out of pre-revenue” (?)

Six-Three

https://six3.tv/

Simon Frost, CTO @spli

  • started out as a private closed network — a messaging thing
  • sports stars started using it to keep in touch with their public, but also to communicate with their private street marketing teams
  • made it onto WAYRA Telefonica business incubator

Thursday, 25 October 2012

MomoLondon: HTML vs Native

A lively and exciting debate (despite the old material!), well-run by Ewan MacLeod, Editor, Mobile Industry Review @ew4n

Panel

Team HTML5

  • Andrew Betts @triblondon
    • HTML5 apps for FT
  • Simon Arora, Biz Dev Mgr, Keynote DeviceAnywhere @devanywhere
    • Initially all about native
    • More and more customers asking for HTML5
    • More platforms with a single codebase
    • No need for appstore or marketplace certification
    • Wider reach to monetise services
  • Jose Valles, Head of Bluevia @josevalles49
    • Been an HTML5 supporter for a long time
    • Launching FirefoxOS device

Team Native

  • Alex Caccia, President, Marmalade @marmaladeapps
    • one of the leading cross-platform build platforms
    • take advantage of ARM instruction set…
    • two of top three games in US app store built using marmalade
    • HTML5 just doesn’t provide enough power - need native for performance
    • HTML5 does not solve fragmentation
  • Chris Book, Bardowl @bookmeister
    • native gives close access to device APIs
    • deal with different network situations
    • HTML5 doesn’t work for audio streaming and caching
  • Nick Barnett, CEO, Mippin @docnickb
    • make app builders for operators and manufacturers
    • provide both HTML5 and native app builders
    • it’s more about the business model and distribution
      • if you want to be in the app store, you have to be native

Last app you paid for?

  • AB: Open House London
    • because their website is appalling and doesn’t work
  • SA: Travel Deluxe
    • native london travel
  • JV: probably a skateboarding app, or tripit or spotify
  • AC: Expense Calculator
  • CB: New Star Soccer
    • 10 games free, then in-app purchases
  • NB: International Rules of Yacht Racing
    • native

All native apps. If you want to buy an app, it has to be in an app store…

What about Facebook?

  • AC: Hardware platform is moving faster than anything else
    • If you come up against an issue, you’re against the browser
    • The only way past is to know the details of the insides of the browser
    • Can’t solve it by logic (terrible for project management!)

FT web app UX

  • EM: FT webapp has to go through local cache expanding step before starting
  • AB: equivalent to installing an app from the store
    • if you say no, it still works; but in a potentially limited way
    • actually a benefit: allows levels of access

Stats from deviceanywhere

  • SA: out of 100 customers, top 25 are looking at HTML5
    • have a lot of enterprise customers
    • looking to increase their reach
  • NB: these customers already have iOS and Android apps?
  • SA: yes, looking to extend reach across devices without decent appstores

HSBC Business Banking

  • EM: it’s an utterly crap HTML5 experience
    • banks say they’d love to do HTML5, but security say no!
  • JV: why then do they have online banking?
    • want to keep customer experience
  • CB: native NatWest app is better than web experience…
    • haven’t been able to update their website in 12 years!
    • loads of apps where you use native app first rather than web site
      • e.g. Hailo, National Rail Enquiries
  • NB: cross-platform HTML5 is a nonsense
    • at Mippin, we build web app builders for each platform separately
  • AB: that’s just ‘cos you’re not doing it very well!
    • FT use same codebase for Android, iPhone, iPad
  • NB: but Windows Phone 7 UX is completely different from iOS
    • customers expect something different
    • so you need to write your UI differently anyway
    • may as well write it natively each time

How do we resolve vested interests? And designing for format?

  • AB: each format and each channel will have differing expectations
    • if you define your constraints narrowly enough, natively will always be better
    • if you have a broad strategy and vision, then web technology will win
    • what about TV? what about kiosks?
    • a single web technology solution will adapt to those situations
    • single code base works with touch, keyboard and gestures too!
    • at a recent hackday, FT Labs connected a Kinect and controlled the app without touching the screen
    • the FT webapp works in the way that the people reading the paper are used to — independent of device expectations
  • AC: want a fine degree of control over what it looks like and how it behaves
    • in gaming environment, you really want to make the app shine
  • CB: isn’t this all about the 30% that Apple want to take out of the subscription?
  • AB: it’s not (exclusively) about the 30% — it’s more about a direct relationship with the customer
    • enables customers to switch devices without losing their subscription
  • CB: but Spotify have native apps and still go cross platform whilst keeping relationship with customers
  • AB: if Apple changed their rules to say that Spotify would have to give a percentage of their revenue, then Spotify would be stuffed
  • NB: if the Daily Mail went the FT route would people get their news elsewhere?

Is it fair to say that HTML5 is destroying usability of mobile platforms?

  • JV: no, it’s building something
  • CB: Google Maps browser version just not as good as previous native version

Hybrids?

  • NB: mippin use unique per platform wrappers
    • PhoneGap works well for iOS, not so well for Android
    • BlackBerry has WebWorks
    • hardcore gaming is a pretty specialist use case
  • CA: use the right tool for the right job
    • SDK supports HTML5 content within an app
    • and then you can switch out and use the native with ease
  • Audience: built a PhoneGap app and was appalled by performance
    • scrolling 50-100 names was just not good enough

Native provides consistent experience?

  • Spotify on some platforms lets you order playlist, Android doesn’t
  • if been written on HTML5, then would have worked fine
  • AB: people put 70% of budget into iOS
    • then 20% into Android
    • then 5% into Windows and Blackberry…
    • not surprising that non-iOS apps are crap

Discovery…

  • JV: 700K apps in Apple appstore, so discovery there is hard too
    • don’t see a difference
  • AB: FT not in a unique position – shared by lots of big brands
    • for small companies, app store is probably a good thing
    • FT have specialist native apps in the store which point users in the direction of the web app

Prisoners of the market owners?

  • NB: usual retail model: retailer takes 30-40% of revenue
    • and benefits can be considerable!
    • if you’re in Brazil in 2 years time with Boot2Gecko devices, then the mindset could be completely different
  • Dan Appelquist: isn’t that the issue — app stores are dragging us back into the old model that the open internet is breaking us out of
  • CB: yes, the dominance is worrying
    • but it’s a business making opportunity for startups
  • CA: native is not closed
    • hardware manufacturers trying to make best user experience

Security in native?

  • CB: difficult to securely store offline data
    • premium audio streaming is not yet possible in HTML5
  • EM: a bank developer said “the security people want a native app for encryption reasons”
  • AB: why does the online banking not just work on the phone?
    • yes, you can have encrypted storage, but do you need it

Best way in for mobile development

  • NB: use an app template toolkit for a size that fits
    • learn to be a mobile developer…
  • what if you just want to see your idea?
  • CA: most dangerous word when you start is “just”…
  • AB: the reason for the standard layouts on web is ads
    • have to build the design to fit the adverts
    • there’s been a boost in design creativity from moving to new formats
    • you can take that newfound focus on user experience and bring it back to the desktop
    • you’d never expect a mobile app to have big gutters down the side
    • unless it’s an iOS 5 app on an iPhone 5…

Notifications

  • NB: issue for HTML5 apps
  • AB: W3C working on notifications as a spec…

New users from India, China & Brazil won’t be in Apple or Google’s ecosystem

  • NB: won’t be a technology decision — more of a distribution

Javascript libraries?

  • NB: 85% of development in HTML5 apps goes into javascript

Great new debugging suites for Android Chrome and iOS Safari

  • Dominic Travers: great time to develop HTML5 apps!

Will we still be arguing in 5 years’ time?

  • AB: native will always be able to innovate faster
    • web will be behind, but standardised
    • FT’s Android app is partly native for performance
    • as soon as the browser catches up, they’ll remove the native part

Announcements

  • W3C coremob.org community group
  • UKTI Competition Final 29th October
  • 7th Anniversary in November

Tuesday, 4 October 2011

Over The Air 2011: The FT Web app - We've Got a Website for That

Andrew Betts, Assanka @triblondon

  • An app is:
    • responsive design
    • responsive to human interface (mouse, keyboard, touchscreen, TV remote, …)
  • The Daily app is now generating less than 50 tweets a day (and still going down)
    • Down from over 200
  • iPad web app also works on other devices
    • not just tablets – phones too
    • currently only accessibly on iPad
    • works on Android & QNX but not released yet
    • Android imminent, QNX a few months
  • server serves the same code to all devices
    • client does customisation and caches as much as it can
    • so can go offline and still access pages
  • FT web app
    • 8 months with 3 people
    • then additional 4 months with same people to get Android & Playbook

issues

  • flowed columns and flowing text around fixed elements
    • adobe webkit fork has great flow additions - but not available on devices
    • css3 template layouts – but again not supported
    • so have to measure content and cut it into positioned containers using Javascript
  • content balancing
    • always show a whole number of items across the width
    • done by classifying devices into four groups according to screen size
      • small, medium, large, large wide
  • podcast pages
    • want to keep playing audio even when move to another page
    • put audio player at the top of the DOM, so not altered
    • entire app is in a single page – just swap content in and out
  • swiping between sections
    • continuous carousel made out of three divs
    • middle one is always the current
    • outer ones are preloaded as required
    • implemented swipes using touch gestures
    • have to do your own gesture interpretation
      • distinguish between slow drags and flings

tools

  • playbook has remote web debugging
  • WeinRE can do similar, but can’t debug Javascript
  • TouchScroll allows you to keep headers fixed and snap to columns when swiping across
  • web debugging proxies (e.g. Charles)
  • use desktop for layout, but real device for interaction (swiping)

discoveries

  • people use native apps differently
    • they tap lightly and fast
    • the web browser waits for fast taps in case there’s a double tap to zoom
    • if you don’t want double tap to zoom
    • Assanka made fastclick

offline access

  • launching app offline
    • need to specify URLs in app manifest
    • if you change a single file, all of the manifest needs to be re-downloaded
    • store as little as possible
    • the more you store, the longer your app will take to launch
    • iOS manifest is buggy – you can get name conflicts with other webapps
      • so make sure you give your manifest a custom name
    • development is hell – things get cached the whole time
      • instead, add a comment that changes every minute (for dev)
      • still leaves you time to refresh a few times to check the cacheing
  • manifest is no good for editorial content
    • local storage is much faster than SQLite
    • so if you only access by key then use it
    • you need permission to store > 5Mb
    • strategy:
      • launch app from web, just store <= 5Mb and prompt to save to home screen
      • saved from home screen, immediately ask for 50Mb and never ask again
    • images downloaded from server as base64 encoded strings
      • can combine images into single requests
      • and can then gzip the whole thing
      • stored in local SQLite
      • rendered into DOM as a data: URI
      • base64 transfer also avoids operator image recompression!
  • analytics
    • can’t use Google analytics
    • log user actions into local DB
    • POST the log when requesting updated content
    • on the server, rewrite the log into an Apache format access log

unresolved issues

  • SSL security: no browser chrome, so no browser padlock
    • trusted, because we tell you…
  • Social media integration – OAuth in separate window doesn’t work
    • have to reload completely when return to app
  • offline adverts:
    • not technically hard, but ad server companies don’t know how to deal with them
    • can’t retract the ad
    • can’t measure clicks
    • can’t click through at all…
  • automated QA – selenium doesn’t really work
    • ended up using lots of people and lots of devices

platforms

  • Android is by far the poorest web environment when compared with iOS and QNX
    • mainly due to lack of hardware-accelerated CSS transitions
    • so FT have a native Android app which has a single native component – the gallery to enable swiping
    • the rest of the app is HTML/CSS/JS
  • QNX has a native app too, but only to have a home screen icon and to provide distribution

Q&A

  • upset Apple?
    • probably not – FT are specific market
  • differences between web app and native
    • web has more sections than native ever had
    • web app preloads content, so people swipe more often
    • as a result web app gets much more interaction
  • is not appearing in the app store an issue?
    • yes, but instead making tactical native apps
    • e.g. FT Top 100 Companies – tells users if you want the full edition, go to the web app

Over The Air 2011: Crap! It doesn't quite look right!

Or… how I learned to stop worrying and set my web sites free

Lyza Danger Gardner, co-founder Cloud Four @lyzadanger

  • Founder of Cloud Four in 2007
  • Explicitly for mobile web
  • Lyza was on the team that built the Obama app
  • Went through the app and realised that there was nothing in the app that couldn’t be done with the web
  • hautelook.com – high performance mobile web
  • deschutes brewery – one web
    • uses geolocation to find where to buy the beer
  • mobile web is hard and getting harder
    • and it’s not just phones any more…
    • car radios, televisions, …
  • and there’s a whole stack every time (any of which can change)
  • in the 1990s, took print ideas and applied them – pixel perfect
    • customers believed that we had control…
    • “could you move the logo a half pixel to the right?”
  • no one can possibly know enough – devices are continually appearing and you still have to deal with the old stuff
  • how do you deal with WYSIWYG for customers…?

mobilewood

  • 10 highly experienced mobile developers
  • working on where we wanted the mobile web to go
  • built http://futurefriend.ly
  • three pages, two images, no interactivity
  • 100 man hours
  • -> not scaleable!

testing is very hard

take heart!

  • relinquish control over a few things we thought we had down pat

  • four considerations:
    1. content like water
      • consider wireframes that demonstrate the flow and flex of content across a continuum of device and window sizes
      • design approach: like proportion – not pixel perfect
      • build functional mockups, so you can show (not tell)
      • it will be an iterative process
      • will not be an overnight change – it’s not a brochure, despite what we told you earlier
      • it’s often surprising how willing customers will be to adapt or modify their content APIs
      • try using textile or markdown in CMS
    2. essentials first
      • not just mobile – pare down to the essentials
      • not just about design – about process, performance, experience for every user
      • start serene and simple
    3. arm the weapons!
      • responsive web design
      • fluid media: 100% width images
      • fluid grids
      • use media queries to enhance (mobile first)
      • see also Responsive Images (by Scott Jehl)
      • Boston Globe is a showcase
      • it’s ok to leave unmanaged gutter in % widths
      • use Modernizr’s modular approach (don’t test everything)
        • but it’s not infallible
      • use server-side work:
        • reordering – moving navigation around
          • android devices are too buggy
        • reduction – smaller images
        • respect – your users: don’t download graphics if you don’t use them
      • user agent sniffing – it ain’t perfect, but it gets the job done
      • don’t be afraid to do some server-side optimization
      • optimise!
        • especially your htaccess or apache config
        • use YSlow
        • make sure you gzip everything you can (not just html)
        • cache manifests are a little tricky to deal with
      • Cloud Four images:
        • server side sizing using WURFL for major sizes
        • common images are then cached
        • then 100% fluid sizing
    4. draw the line
      • set expectations with your customers
      • explain how you don’t have control over everything
      • don’t be afraid to pull out egregious hacks!
      • be ready to fail gracefully
      • this isn’t religion!
  • frameworks:
  • iOS rotation
    • use -webkit-text-size-adjust:none;

Lyza is writing a book – Head First Mobile Web

Thursday, 8 September 2011

iOSDev UK: Real-World Data (or There and Back Again)

Hamish Allan, Olive Toast

The story of writing Files Pro — an app to take files with you on an iOS device.

  • Used Deusty’s CocoaHTTPServer
  • Dropbox has a nice API
    • operations are aynchronous
  • Gamekit makes device to device connection over bluetooth easy
  • Could use HTML5 to make a PC-based interface to an iOS app
    • Visit a web page served from the device from your PC and see a flexible app within your browser
  • iCloud
    • NSFilePresenter tells you when a file transfer has completed
    • iCloud syncs the meta-data about files first, using NSMetadataQuery
  • “Your market is not power users”
  • Apple is moving towards a flat list of files with search, rather than a hierarchical system

Q&A

  • No hooks in iOS for AirDrop (yet?)
  • Nor any GameKit APIs which talk to desktop

Monday, 11 October 2010

MomoLondon: Demo Night

I’m catching up on blog posts slowly. This one’s the Mobile Monday London Demo Night from 13th September… Together with Ewan and Sergio (manfully representing FuturePlatforms), I was presenting my Over The Air hack from the weekend (see previous post) and I was consequently suffering from a lack of sleep. Here’s a quick run down of the other presentations:

psonar

http://www.psonar.com/

  • upload music to psonar
  • get at music on any HTML5 connected device by streaming or downloading

roulette cricket

http://www.roulettecricket.com/

  • great idea
  • impressive implementation by FuturePlatforms, as usual…
  • £2.50/month to play for prizes, or a revenue share from bets

HipSnip

http://hipsnip.com/

  • mobile notepad for the things you want
  • enhanced with smart searches & geolocation:
    • wine.com, cnet, imdb, yelp
  • mobile design a little too small for hands… need to follow Apple HIG on Android too :-)
  • user research: found that people take photos, or save a draft SMS but then forget
    • wanted to have a way to remind people

The logo is an aleph. Is that for infinity or for hebrew? The letter carved into the head of the golem…?

Toshl

http://toshl.com/

  • personal expense record
  • quite secure
  • have apps for android, iphone & maemo
  • sync to web
  • on web, can analyze, export
  • currently 45,000 users, 1/3 active
  • iPhone downloads in 3 weeks almost surpassed Android’s 6 months
  • are in negotiation with banks for auto-download
  • currently have a freemium model, looking for investment from banks for rebranding
  • some great observations:
    • RIM apps generally look ugly
    • front end and usability on mobile apps takes 50% of development time
    • cross platform development is nose bleeding expensive!

Collinson Group

http://twitter.com/mtjmelody

  • Columbus Insurance is one of their brands
  • a mobile trip planner
    • but with a surprisingly comprehensive offline database of airports, flight plans, hotels and car hire
  • had a desktop version for quite a few years, just brought across to Apple platform

Appmarks

Adrian Cuthbert

http://www.myappmarks.com

  • bookmarks in that point to specific places within apps
  • want to add Android version too
  • if app not available, offers to download it from store
  • would like apps to supply relevant info

Milestone Planner

Benjamin Ellis

http://milestoneplanner.com/

  • need a plan, but things change very fast
  • wanted a plan on a page that everyone could update
  • webapp written with HTML5 and javascript
  • server keeps a full history of all changes
    • can view as list in webapp, RSS, export to twitter
  • facilitating a discussion around the plan
  • automatically generate weekly reports in PDF
  • most planners are based on TODOs, this is based on outcomes and people instead, larger scale

Qootia

tomaz@qootia.com

  • big screens that people can interact with by making voice phone calls
  • good demo, with great timing from the presenter

Liquid Air Lab

http://twitter.com/spodtronic

  • 480 apps developed on most popular smartphone platforms
  • 7.8 million users
  • 33,000 downloads per day
  • Android users are little more techie
  • BlackBerry users especially in the US
  • Nokia user… is catching up fast… !?!?
  • Ovi store has overtaken iPhone share
    • (since they have a special category for Radio apps…)
  • iPhone is going down in share compared to the others
  • started on Symbian and moved on to iPhone, etc
  • now have 7 platforms…

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.