[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[mobile-iwg] Minutes of MIWG call November 18th
|
List of Attendees
Thomas Westling Eclipse team leader Sony Ericsson
Rich Barlett Director S60 tools, Nokia
Mark Rogalski eRCP project, IBM
Joe Green Monta Vista
Chris Intel
Henry Microdoc
Wayne Parrot Genuitech
Todd Williams Genuitech
Craig Setera MTJ, EclipseME Projects
Eric Cloninger TML Project Lead, Motorola
Dino Brusco Sr Director Developer Tools, Motorola
Christian Kurzke MTJ Project Lead, Architect, Motorola
Lori Fraleigh Motorola Studio Tools Mgr, Motorola
Dino Brusco presenting the slides: (available from Mailing List)
Scope of this call: Introduce and give overview of Mobile Industry
Working Group (MIWG)
Motorola and Nokia have been collaborating to put together the Charter,
Links posted on mailing list
Brief overview: Eclipse for Mobile Industry:
Focus on Application development for mobile devices
Not current WG scope: Phone bring-up, embedded development, Platform
Development Kits
Summary of Industry Needs:
Each manufacturer has different application platforms for specific
handsets, for example: Nokia, Motorola, SE have all different platforms.
As a result, tools providers (often Manufacturers, but also 3rd party
tools providers) re-invent the wheel in order to target the different
handsets.
Also learning curve of developers USING those tools, developing for
cross manufacturer applications.
Current Problems: High switching cost for application developers, less
than optimal tools for each platform.
Slide 2:
Goal of this WG: Collaborate on a generic base set of Application
Development (ADK) tools.
Benefit to App developers: Lower switching cost, lower overall
development cost, quicker time to market.
Benefit to Manufacturers: Lower development cost when basing tools on
generic Eclipse ADK
Still: Manufacturers need to be able to customize the base ADK, by
adding device specific "profiles".
This WG is a forum for developers, manufacturers, tooling providers to
collaborate on this goal.
Key Output: Creation of road map for evolution of this common ADK.
Intent: Adoption of this base ADK across the industry.
Current State: recruitment of key participants to WG.
Slide 3:
Product: Define and implement a common ADK platform.
goals:
A packaged product which a end-user developer can download.
Roadmap, complementary offerings
Best practices, test suites, testing criteria
Consistent marketing message, promote mobile ADK, collaborate with
eclipse marketing team
Slide 4:
Today's application developer has no clear starting point on Eclipse
website, many "applicable" projects, no packaged product.
Vision:
- Provide a packaged product "Eclipse Mobile ADK" for developer
download.
- Offer support for native, Java and web mobile application development.
- mobile ADK as the "default" environment to be targeted by mobile
specific add in providers
Slide 5:
Goal of a high level architecture is to identify possible shared
components which benefit developers and tools providers.
Slide 6:
Overview of current WG status, links to web resources
Immediate action items: Define WG roadmap by Q1/09
Discussion, Q&A:
Question: Has Google been involved to join the MWG:
Answer: (Dino/Christian) Android is certainly a fitting Platform to be
considered in the Mobile ADK.
We're in progress to work on a value proposition for Google.
Call for action, if anyone has contacts in Google, give feedback and
make Google aware of effort.
