Beginners Guide to TikTok for Search - Rachel Pearson - We are Tilt __ Bright...
Why AppUp? A Quick Review of the AppUp Model
1. beta
Intel® Atom™ Developer Program
Part of the Intel® Software Network
Originally published as a blog by Bob Duffy at :
http://appdeveloper.intel.com/en-us/blog/2010/08/22/why-appup-quick-review-appup-model
Why AppUpSM ? — A Quick Review
of the AppUpSM Model
Intel launched a beta version of its AppUpSM Center online store in January in 2010. Under the beta program
developers have known AppUpSM as a single storefront primarily supporting netbook applications developed in C/
C++. Unfortunately, this history does not put the overall value of AppUp in proper context. Here's a look back and
forward to help you know what to expect with AppUp.
Why app stores matter
The launch of recent smartphone app stores is relevant. Smartphones are a new
computing device that require a new service to sell, distribute, and purchase apps for
that device. Existing solutions do not suffice. These new phones required a single and
convenient gateway to browse and purchase verified applications for that device. With
this new app store model you can, within seconds, anytime and anywhere, have an app
working on your device. No longer do you need to hunt across many websites, using a
variety of installers, with disparate reviews and different methods for purchasing the
app. There is one standard for distribution, search, browsing, rating, purchasing, and
installing applications. This makes it extremely easy and convenient for consumers and
developers.
The app store gap The AppUpSM model
However, the market is evolving. Devices This is where AppUp comes in. AppUp is
come in all flavors, sizes, and shapes. A an app store framework designed to allow
store per manufacturer, per carrier, or developers to submit apps or app compo-
devices will again lead to fragmentation. nents to stores that serve various devices
What about when we get apps on our and operating systems, where those apps
TV’s, netbooks, PC based tablets, and are sold by various manufactures, service
other smart consumer electonics outside providers, and retailers. And from a con-
of the smartphone model? How do we sumer’s perspective, we allow for them to
get those apps as conveniently as we do have the AppUp client installed on multiple
on our phones? And what if I have apps systems where their existing purchases
purchased from my PC, or TV and now I’m are tracked and available for download
on the road using a netbook and I want across compatible systems.
that app? Also, what if you, as a developer,
So with AppUp you get the benefits of
create a new service or capability that
what Apple started with their AppStore,
helps deliver solutions for the store and or
along with the opportunity to distribute
developers?
and buy apps across manufacturers, ser-
What’s missing is a model that allows vice providers, and device types.
developers to get their apps and compo-
nent services into a store framework for
distribution across many devices, many
manufactures, and service providers,
while also allowing consumers to get ac-
cess to apps they may have purchased on
other devices.
2. White Paper Title Placeholder Here
beta
Intel® Atom™ Developer Program
Part of the Intel® Software Network
The start of AppUp development for AppUp. For Windows* realized. At the moment we are in beta,
apps we allow wrappers to be imple- soon to release AppUp more broadly, so
AppUp needed to start somewhere. For mented around any language or runtime it’s too early to tell how well AppUp will
Intel, netbooks represent a large existing that Windows can support. Thus, if your help developers make money. We believe
market of computing devices that lacked app is not written in a language our SDKs the potential to monetize applications
apps verified to work well for a netbook. support then a wrapper solution allows is ever increasing with AppUp. We also
As of 2009 nearly 40 million netbooks you to use one of our natively supported believe there is a huge opportunity for
had been sold, more than iPhones. And languages as a layer in your application developers to create and sell solutions
research predicts 150 million netbooks in for our SDK. Meanwhile, your app runs in that help other developers monetize and
the market by 2014. Within 8 months of its native environment. The message here distribute applications. We are seeing
the beta program we are well underway, is that choice is at the cornerstone of the this already with a few of our developers
with over 700 netbook apps in the AppUp AppUp model. You can develop apps using expanding beyond their core business by
Center. Additionally, the AppUp store the tools, languages, and runtimes that selling services and component solutions
allows clients to be installed using 1 best suit your app needs. to AppUp developers. Perhaps the best
account on up to 5 netbook devices. Thus, option for developers is to consider the
each of those netbooks has access to all Broadening OS, device, and groundfloor opportunity for AppUp as it
apps purchased under that account. storefont options evolves beyond beta. Those who deliver
Currently, AppUp supports Windows and the early apps and early core services and
In terms of development environments,
Moblin™ aligning with the prevalent OS’s components will in all likelihood translate
we started with C/C++ and Windows*
for netbooks systems. As we broaden Ap- to earlier success for those developers.
support for our SDK. Again, this was a
starting place, as netbooks this provided pUp to other devices, our support for op-
the broadest solution for that community. erating systems will also broaden. MeeGo Developer feedback
The SDK for our beta program has been is a new, full-featured OS that is designed I am very much cognizant that my words
very lightweight and primarily focused to support netbooks, new smartphones, on AppUp go so far. After all, I work for
on establishing app initialization and tablet devices, smart TVs, and more. Intel Intel and am part of the program. As
authentication to ensure the app was and Nokia announced MeeGo as the next- the community manager, I’d rather have
bought and properly licensed for use on generation OS that marries the best of others explain how they see it. Here are
the system running it. Moblin™ and Maemo* operating systems. thoughts from some of our developers in
Shortly after, in May, the netbook version response to the question, “Why AppUp?”
Intel also recognized the need to allow of MeeGo was released. In October the Feel free to add your own thoughts on
our community to build on the value of handset and tablet versions of MeeGo is “Why AppUp?” by adding your comment
the marketplace by creating services and slated to be released. Things are moving and or a link to your own YouTube* answer
components that will help developers quickly, and we can expect an AppUp cli- on Why AppUp?
build and sell their apps. With the beta ent to follow for each of these devices.
program Intel created a developer catalog
On the store-front side of things, the Ap-
and marketplace within our community.
pUp Center beta store launched as an Intel
This is already paying dividends for Intel
store. However, as expressed earlier, the
and developers. To date, we’ve seen
model is to partner with manufacturers,
solutions that are enabling a broader set
services providers, and retailers to white
of apps to get into the store than the SDK
label or rebrand the Intel AppUp Center.
alone enables.
As much as Intel would like to disclose
Broadening developer what store-fronts will be coming, we
environments have to respect the relationships with our
Beyond C/C++ we have recently enabled partners before we disclose a roadmap
Adobe’s AIR* runtime, and we are very of these agreements. So stay tuned for
soon to release a .NET SDK. As well, Silver- more information on where you will find
light and Java are near-term solutions for additional AppUp stores.
AppUp development. Show me the money
However, these supported languages and In the end, none of the above matters
runtimes are not the boundaries of app much if monetization of apps is not
2 2
3. White Paper Title Placeholder Here
beta
Intel® Atom™ Developer Program
Part of the Intel® Software Network
Mike Kasprzak
Chris Skaggs
Lee Bamber
3