1. Develop Meego Application for Intel AppUp℠

2. Create MeeGo* Applications for Intel AppUp℠ Center
Agenda
Create MeeGo* Applications for Intel AppUp℠ Center
Intel AppUp℠ Center & Developer Program
Create Applications for Intel AppUp℠ Center
Review Sample Applications
Summary
Q&A

3. MeeGo Working Model Open Source Projects MeeGo.com
3rd Party Apps
Closed Source
Upstream Open Source Projects
MeeGo.com
Codecs
Community Distro,
build environment,
SDK…
Commercial Solutions
MeeGo Core
Net* Reference
MeeGo Projects
Operating System Vendors
Build Environment
MID Reference
IVI Reference
OSVs provide
Complete Stable Image
Final integration / validation
Technical support / debug
Custom patches / updates
Additional documentation
Sustaining engineering
OSV charge for the following based on OEM needs:
Integration of close source components; Moblin provides all open sources software and several closed source components are required to complete a distribution for an OEM platform. Some examples are closed source codecs as well as closed source drivers for components used in the OEM platform. These closed source components may be made available by the OEMs, however, the OSV has to ensure these components are integrated in the distribution.
Customizing the UI per OEM requirements; Moblin provides a rich application and UI framework based on Clutter technology; however, the reference distribution on moblin.org would include a basic reference UI; OEMs would prefer to customize the UI to deliver a rich end-user experience that can be made possible with the moblin UI framework and OSV can provide this service.
Develop additional middleware or applications per OEM requirements; these could be either or both open source applications modified/optimized to work with the rest of the stack in the distribution
Integration and validation of all Moblin and non-Moblin components on OEMs platform; The validation of the Moblin reference stack will be typically done on Intel customer reference boards and not necessarily on specific OEM platform; in order to make sure the Moblin distro put together by the OSVs is qualified on the OEM platform, the OSV and/or the OEM need to do complete validation on the final platform.
OSVs also may localize for geographic markets, coordinate upstream community activities, ensure legal compliance, and manage file and security updates.
Last but not the least is the on-going support to an OEM on all associated software services ranging from bug-fixes, enhancements and software refreshes for subsequent platforms.
Device Vendors
MeeGo.com hosts the core technology development and open source distro
Commercial OSVs deliver customized “compliant” products 3 3

4. Intel AppUpSM Developer Program and Intel AppUpSM Center
Begin with a definition of the Intel AppUp developer program and the Intel AppUp center and how they work together.
Intel AppUp developer program provides developers with the tools, resources and incentive and recognition programs to create superior apps to be sold in the Intel AppUp center.
The Intel AppUp center is the store where the apps are sold to consumers. The Intel AppUp developer program is the door to submit apps into the Intel App Up center. 4

5. Intel AppUpSM Center Model
OEM
Service
Provider
Retailer
Partner Market place
Smart TVs
Desktops
Embedded
Netbooks
Handhelds
Intel AppUp center and developer program span the compute continuum. This slide demonstrates the flexibility of the program.
Personal Devices
Tablets
IVI
Laptops

6. Intel AppUpSM Center & Developer Program
Compatible HW
Users
Developers &
Applications
Operating
Systems
App Store
Developer
Framework
For Consumers
Intel AppUpSM center + OEM/service provider co- branded app stores
Rich catalog of applications
For OEMs/Retailers/Service Providers
Intel AppUpSM center for TTM
Intel drives ISV recruitment & dev
Co-branded store with revenue share
App store scalable to future devices: smart phones, handheld, embedded
For Developers and ISVs
Tools, SDKs for MeeGo*, Windows*, and various runtimes
New sales channels
Support for multiple devices
The Intel AppUp Developer Program and Intel AppUp Center is an end to end economy.
Consumers have access to a rich catalog of applications . They have access to Intel’s store, but eventually co-branded OEM and Service Provider stores as well. They can buy apps once and run on up to 5 devices.
The Intel AppUp Center will enhance product and service offerings for OEMs and service providers, allow them to remain competitive across all segments and generate revenue. They are along for the ride, with skin in the game
Developers and ISVs reach a broad audience including OEM & Service provider customers while billing and licensing is covered by Intel. Additionally AppUp center supports native apps, and apps created on runtimes like Adobe Air. So no need to learn new languages.
The Intel AppUp center launched with the Windows OS and will soon be supporting MeeGo apps.. If before MWC. If during or after MWC, is now accepting applications for MeeGo for tablets and netbooks.
Now we’ll take a deeper look at MeeGo and how that fits onto our application strategy

8. MeeGo Spans Multiple Segments
Netbooks
Tablets
Smart Phones
Smart TVs
Embedded
Intel® AppUpSM Developer Program & Intel AppUpSM Center
Single Unified Operating Environment
MeeGo is a continuation of the Intel Atom processor software strategy execution. It fits nicely into our application continuum strategy. MeeGo’s common APIs make it easy for developers to port applications across multiple devices.
Platforms based on Intel® Atom™ processors
MeeGo is a continuation of the Intel Atom processor software strategy execution 8 8 8

9. Settings Database GConfUX
OS Middleware
MeeGo Architecture
Netbook UX
Netbook UI + Apps
Netbook UI Framework
Handset UX
Handset UI + Apps
MeeGo Touch Framework
Other UX’s
Other UI + Apps
Other UI Framework
...
MeeGo APIs
MeeGo WebRunTime
Qt Toolkit
OS Base
Settings Database GConf
System Libraries
glibc, glib, etc
Message Bus
D-Bus
HW Adaptation Software
Platform Info
libudev
Linux Kernel
Comms Services
Telephony
oFono
Connection Mgmt
ConnMan
VOIP, IM, Pres.
Telepathy
Bluetooth
BlueZ
Internet Services
Layout Engine
WebKit
Web Services
libSocialWeb
Web RunTime
Location Services
Visual Services
3D Graphics
OpenGL / GL ES
2D Graphics
QPainter X
GTK / Clutter
Media Services
Media Framework
GStreamer
UPnP
GUPnP
Codecs
Gstreamer plug-in
Camera
Audio
PulseAudio
Data Mgmt
Context Framework
ContextKit
Content Framework
Tracker
Package Manager
PackageKit
Device Services
Backup & Restore
Device Health
DSME
Resource Mgr
System Policy Mgr
Sensor Framework
SensorFW
Personal Services
PIM Storage
Evo DataStorage
Accts & SSO
Accts-sso
Device Sync
SyncEvolution
SECURITY
MeeGo Core
The MeeGo OS Base layer contains the Linux kernel and core services along with the Hardware Adaptation Software required to adapt MeeGo to support various hardware architectures.
The MeeGo OS Middleware layer provides a hardware and usage model independent API for building both native applications and web run time applications.
The MeeGo User Experience layer provides reference user experiences for multiple platform segments; the initial MeeGo release will contain reference user experiences for handhelds and netbooks and additional platform segments will be supported over time.
Hardware Adaptation Software There are multiple software components that a hardware vendor must provide for MeeGo to run successfully on their platform architecture, including platform kernel drivers, core architecture additions, kernel configuration, X software additions and configuration, modem support, and hardware specific media components

10. Intel AppUpSM SDK Suite 1.2 for MeeGo*
Developer Essentials – the MeeGo SDK: Everything to develop on Windows and Linux host platforms - the MeeGo OS, Emulator, GNU Toolchain, etc.
Create, Test, Tune and Publish Apps To Intel AppUp Center
Start Your App Development For MeeGo* Today: SM

11. Development Environment
Host Development Environments
Intel AppUpSM SDK Suite 1.2 for MeeGo*
MeeGo SDK 1.2 for Windows* and Linux:
Qt* Development Tool Chain
Intel AppUpSM SDK for MeeGo*
Application Tuning Tools:
Intel® VTune Amplifer XE for Meego*
Intel® C++ Compilers for MeeGo*
Target
Intel AppUpSM Center Client for MeeGo*
AppUp center 2.5 Alpha for MeeGo Tablet
AppUp center 2.5 Beta for MeeGo Netbook
The MeeGo SDK for Windows includes all of the required software that you will need to develop a MeeGo application on Windows. This includes a modified version of Qt Creator that has been integrated with a compiler targeting the MeeGo environment.
Note, that if you download Qt Creator for Windows from the Nokia site, it will compile Windows applications not MeeGo applications. So if you are developing MeeGo applications be sure you download the Intel version from the Intel app developer site.
Want emulator, then 32-bit only (and possibly some CPU compatibility issues)
Have target HW, then you can go 64-bit and use remote debugging
Windows development environment requires 32-bit based Window XP* or Window 7* for emulator to work

12. Qt for Meego Supported Platforms Windows*, Mac*, Linux*, MeeGo*
Technologies
IDE: Qt Creator
Cross Platform API; Native C++ Implementation; QML/QtQuick
Touch & Gestures
License Models
Commercial, GPL, LGPL

13. Qt* Development Toolchain
Qt modular class library
Qt development tools
Qt Creator Cross-platform IDE
QMLViewer
QtQuick/QML
Core GUI WebKit Graphics View Scripting OpenGL
XML Multimedia Database Network Unit Tests Benchmarking
Qt Designer Gui designer
Qt Assistant Help reader
Qt Linguist I18N
Toolset
qmake Cross-Platform Build Tool
Cross-platform support
Windows
Mac
Linux/X11
eLinux
Win CE
Symbian

14. QtCreator* – Qt* Cross Platform IDE

15. GNU Tools MeeGo supports all standard GNU toolchains such as gcc, gdb.
Recommended gcc compiler flags for performance and optimization:
-march=atom -mtune=atom -O3 –flto –ffast-math
More Info:
Intel® 64 and IA-32 Architectures Optimization Reference Manual

16. MeeGo* SDK for Windows*
Provide the same environment as a MeeGo* OS runtime – allows development without actual device Offers both Window* based and Linux* based installation with an active community support (forum, wiki etc…) Standard Installation: Virtual Meego tablet or Network in Oracle Virtualbox, Qemu emulator, QtCreator (special MeeGo* edition), latest MeeGo* image Available to download from

17. MeeGo* AppUpSM SDK for Windows*
Dependency: MeeGo* SDK Offers C and C++ API Standard Installation: API Libraries, Documentation, QtCreator setup, RPM packaging Intel AppUpSM Software Debugger
Intel AppUpSM Software Debugger to get an ADP_AUTHORIZED, ADP_AUTHORIZATION_EXPIRED response back

18. Instrumentation Crash Reporting AppUpSM SDK Services
Authorization
verify that end-user device is authorized to run the
application
Instrumentation
record application’s usage statistics and post it on
developer’s dashboard
Crash Reporting
registering all crashes
attempting to collect crash data (such as call stack)
reporting statistics and crash data on developer’s dashboard
-Piracy

19. Application Beta Testing - AppUpSM Center
Beta app will appear in your account under “My Apps”
Install and launch your app to test it 19

20. AppUp SDK Contents
Intel AppUpSM software libraries for C++ The Intel AppUpSM Software Debugger to aid with debugging Code Examples to aid in the development of C++ applications Documentation to show you how to incorporate the appropriate API calls into your applications

21. Developer Platform

22. SDK Libraries
SDK libraries provide you with access to the Intel AppUp™ center client software for services such as Authorization, Error and Warning Handling, Instrumentation (metering), Upgrade Authorization, and Crash Reporting. SDK libraries are the only parts of the SDK that are redistributed with applications. There will be separate implementations of the library for each supported runtime and, in the case of native applications, for each supported operating system.

23. Intel AppUp™ Software Debugger
The Intel AppUpSM Software Debugger is a utility that emulates the Application Services of the Intel AppUpSM center client software. The Intel AppUpSM Software Debugger allows you to test and debug your application without requiring the full client stack or access to hardware. The Intel AppUpSM Software Debugger can also be copied to your target MeeGo device for debugging there.

24. Packaging Integration
Packaging Integration allows you to integrate and package application RPM executable or configuration files, SDK library files, and manifest into a single RPM package file for upload to the Intel AppUpSM developer program portal. For this SDK, Qt Creator supports RPM packaging integration.

25. Getting Your App in AppUpSM
Join the Program
Join Intel AppUpSM developer program
Download SDK Suite
Set-up your development environment
Download Intel AppUp™ SDK Suite 1.2 for MeeGo*
Create App
Create, Test and Tune your app using Intel AppUp™ SDK Suite 1.2 for MeeGo*
Submit App
Submit your app to Intel AppUpSM developer program for validation

26. Detailed Development Flow

27. Detailed Development Flow (continued)

28. Get Started Become a member of Intel AppUpSM developer program
Enroll at appdeveloper.intel.com
Benefits: Worldwide distribution channel, development support, low barrier to entry infrastructure, easy validation
Create, Test, Tune and Publish Apps To Intel AppUpSM Center
Intel AppUp™ SDK Suite 1.2 for MeeGo*

29. Instrumentation AppUpSM SDK Services
Authorization
verify that end-user device is authorized to run the
application
Instrumentation
record application’s usage statistics and post it on
developer’s dashboard
Crash Reporting
registering all crashes
attempting to collect crash data (such as call stack)
reporting statistics and crash data on developer’s dashboard
-Piracy

30. Packaging an Application for Appup™
Step 1: Verify that the Qt Creator project has statically linked the application to the SDK Library. The following lines must appear in the Qt Creator application project (.pro) files:
INCLUDEPATH += "$$(IADP_SDK_DIR_MEEGO)Cpp\include"
LIBS += -lxml2\
-lpthread
LIBS += "$$(IADP_SDK_DIR_MEEGO)Cpp\lib\libadpruntime.a" \
"$$(IADP_SDK_DIR_MEEGO)Cpp\lib\libadpcore.a" \
"$$(IADP_SDK_DIR_MEEGO)Cpp\lib\libxerces-c.a" \
"$$(IADP_SDK_DIR_MEEGO)Cpp\lib\libxml-security-c.a" \
"$$(IADP_SDK_DIR_MEEGO)Cpp\lib\libcrypto.a"
9/19/2018

31. #include “adpcppf.h” Step 2: Include the SDK Header File
Packaging an Application for AppUpSM (Continued)
Step 2: Include the SDK Header File
In the declaration section at the start of the C++ source file, include the SDK header file reference, as shown below.
#include “adpcppf.h”
9/19/2018

32. Packaging an Application for Appup(SM)continued)
Step 3: For testing and debugging, you keep the following unchanged.
com::intel::adp::Application *pBasicSampleApp = NULL;
try{
pBasicSampleApp = new Application(ADP_DEBUG_APPLICATIONID);
qDebug("Application Authorized to run.\n"); }
9/19/2018

33. Packaging an Application for AppUpSM (Continued)
Step 4: Once your application is working, you will need to get and swap in a Production ID. you must replace the Authorized Application Debug ID with an Authorized Production Application ID before you can submit the application to the Intel AppUp ™ developer program portal. For example, if you received your Authorized Prodcution Application ID as
0x , 0x , 0x , 0x , the line will be as below
com::intel::adp::Application *pBasicSampleApp = NULL;
try{
pBasicSampleApp = new Application(0x , 0x , 0x , 0x );
qDebug("Application Authorized to run.\n"); }
9/19/2018

34. Application Validation
How We Validate Your Application
Check your submission information (rating, categories, submitter notes, intended targets and runtimes, etc.)
Install the application, Run several types of validation tests to check for compliance to the submission guidelines.
Pass or Fail the app and notify the developer of the results.
How to Ensure a Smooth Validation
Review and ensure MeeGo Compliance
Reviewed the Validation Guidelines
Test your application internally before submitting to Intel.
Positive developer experience with transparent validation process and relevant validation results.
Application Install/Launch/Uninstall Check
Intel Trademark and Content Criteria Check
Content and Description Check
Icon and Screenshots Criteria Check
Content Rating Check

35. Advanced Info – API Level
The Intel AppUpSM SDK library provides a mechanism to determine compatibility of the API level of applications versus the API level of client systems. Applications with API levels higher than that supported by the client system are not permitted to be downloaded to the client

36. API Level – Debugger Output
API level information for an application is displayed in the Intel AppUp™ Software Debugger output :

37. Application Beta Testing
Test your app live in the AppUpSM center, but app won’t be seen by end user
Improves chances of passing validation without error 37

38. Application Beta Testing
Download AppUpSM Center
Create a user account in AppUp center
Add AppUpSM Center login account in the “Invite” box 38

39. Application Submission
9/19/2018

40. Application Development Process Recap
On a 32-bit Window* system, install MeeGo* SDK (from meego.com)
Install MeeGo* AppUp SDK for Windows* (from appdeveloper.intel.com)
Develop in Qt* Tool Chains such as QtCreator
Test run by three different way:
Meego Emulator under Qemu ( slow)
Virtual Meego in Oracle VirtualBox
A real Meego Device via IP Network
Generate RPM package from QtCreator
(optional) Deploy RPM package on actual MeeGo* device for final testing

41. Backup Slides
9/19/2018

42. More Qt Toolchain Qmake
Help to generate Makefile for compilation Example:
Generate Microsoft Visual Studio project:
“qmake -tp vc yourapp.pro”
Generate Intel® C++ compiler 64-bit mode Makefile:
“qmake -spec linux-icc-64 yourapp.pro”
Generate Mac* Xcode project:
“ qmake -spec macx-xcode yourapp.pro”
Moc
Integrated with Qmake to handle Qt* C++ extensions
Rcc
Integrated with Qmake for bundling static resources

43. Setting up MeeGo Netbook as Development Environment
Install MeeGo
Login to MeeGo, Applications -> System Tools -> Terminal
“sudo zypper refresh” ;
“sudo zypper install –t pattern development-libs development-tools” ;
“sudo zypper install –t pattern x-software-development” ;
“sudo zypper install qt-creator qt-devel-tools qt-designer qt-qmake qt-qmlviewer automoc4”
Other Qt™ packages: “sudo zypper search qt”

44. Recap On a 32-bit Window* system, install MeeGo* SDK (from meego.com)
Install MeeGo* AppUp SDK for Windows* (from appdeveloper.intel.com)
Develop in Qt* Tool Chains such as QtCreator
Test run inside Qemu
Generate RPM package from QtCreator
(optional) Deploy RPM package on actual MeeGo* device for final testing

45. Recap
AppUpSM SDK is optional but highly recommended – DRM, crash reporting, other future offers
Allows C, C++, Ruby, Python, Perl (AppUp SDK only for C, C++)
Must follow MeeGo* Compliance Guideline (from meego.com) and AppUpSM Validation Guideline (from appdeveloper.intel.com)
Accepts MeeGo* netbook apps and MeeGo* tablet apps

46. Summary and Resources
Untapped Intel® Atom™-based devices : Ride the wave of netbooks, tablets, set top boxes and smart phones for Intel AppUpSM Center
Streamlined developer process, lots of support from Intel® AppUpSM Developer Program
Get started today!
App developer portal:
Intel Tools:
Developer incentives and opportunities:

47. Legal Disclaimer THIS PAGE IS REQUIRED DO NOT DELETE
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPETY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL’S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL® PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
Intel may make changes to specifications and product descriptions at any time, without notice.
All products, dates, and figures specified are preliminary based on current expectations, and are subject to change without notice.
Intel, processors, chipsets, and desktop boards may contain design defects or errors known as errata, which may cause the product to deviate from published specifications. Current characterized errata are available on request.
[Add any code names from previous pages] and other code names featured are used internally within Intel to identify products that are in development and not yet publicly announced for release. Customers, licensees and other third parties are not authorized by Intel to use code names in advertising, promotion or marketing of any product or services and any such use of Intel's internal code names is at the sole risk of the user
Software and workloads used in performance tests may have been optimized for performance only on Intel microprocessors.  Performance tests, such as SYSmark* and MobileMark*, are measured using specific computer systems, components, software, operations and functions.  Any change to any of those factors may cause the results to vary.  You should consult other information and performance tests to assist you in fully evaluating your contemplated purchases, including the performance of that product when combined with other products.
Intel, [Add words with TM or R from previous pages..ie Xeon, Core, etc] and the Intel logo are trademarks of Intel Corporation in the United States and other countries.
*Other names and brands may be claimed as the property of others.
Copyright ©2011 Intel Corporation.
THIS PAGE IS REQUIRED DO NOT DELETE

48. Risk Factors THIS PAGE IS REQUIRED DO NOT DELETE
The above statements and any others in this document that refer to plans and expectations for the first quarter, the year and the future are forward-looking statements that involve a number of risks and uncertainties. Many factors could affect Intel’s actual results, and variances from Intel’s current expectations regarding such factors could cause actual results to differ materially from those expressed in these forward-looking statements. Intel presently considers the following to be the important factors that could cause actual results to differ materially from the corporation’s expectations. Demand could be different from Intel's expectations due to factors including changes in business and economic conditions; customer acceptance of Intel’s and competitors’ products; changes in customer order patterns including order cancellations; and changes in the level of inventory at customers. Intel operates in intensely competitive industries that are characterized by a high percentage of costs that are fixed or difficult to reduce in the short term and product demand that is highly variable and difficult to forecast. Revenue and the gross margin percentage are affected by the timing of Intel product introductions and the demand for and market acceptance of Intel's products; actions taken by Intel's competitors, including product offerings and introductions, marketing programs and pricing pressures and Intel’s response to such actions; and Intel’s ability to respond quickly to technological developments and to incorporate new features into its products. The gross margin percentage could vary significantly from expectations based on capacity utilization; variations in inventory valuation, including variations related to the timing of qualifying products for sale; changes in revenue levels; product mix and pricing; the timing and execution of the manufacturing ramp and associated costs; start-up costs; excess or obsolete inventory; changes in unit costs; defects or disruptions in the supply of materials or resources; product manufacturing quality/yields; and impairments of long-lived assets, including manufacturing, assembly/test and intangible assets. Expenses, particularly certain marketing and compensation expenses, as well as restructuring and asset impairment charges, vary depending on the level of demand for Intel's products and the level of revenue and profits. The majority of Intel’s non-marketable equity investment portfolio balance is concentrated in companies in the flash memory market segment, and declines in this market segment or changes in management’s plans with respect to Intel’s investments in this market segment could result in significant impairment charges, impacting restructuring charges as well as gains/losses on equity investments and interest and other. Intel's results could be impacted by adverse economic, social, political and physical/infrastructure conditions in countries where Intel, its customers or its suppliers operate, including military conflict and other security risks, natural disasters, infrastructure disruptions, health concerns and fluctuations in currency exchange rates. Intel’s results could be affected by the timing of closing of acquisitions and divestitures. Intel's results could be affected by adverse effects associated with product defects and errata (deviations from published specifications), and by litigation or regulatory matters involving intellectual property, stockholder, consumer, antitrust and other issues, such as the litigation and regulatory matters described in Intel's SEC reports. An unfavorable ruling could include monetary damages or an injunction prohibiting us from manufacturing or selling one or more products, precluding particular business practices, impacting Intel’s ability to design its products, or requiring other remedies such as compulsory licensing of intellectual property. A detailed discussion of these and other factors that could affect Intel’s results is included in Intel’s SEC filings, including the report on Form 10-Q for the quarter ended September 25, 2010.
Rev. 1/13/11
THIS PAGE IS REQUIRED DO NOT DELETE