TotalCross helps developers to create for more devices than any other platform in the world, not only mobile and desktop but also embedded devices like Raspberry Pi, Toradex and more. In the webinar we show news about our technology and plans for 2020. #devfirst
Mobile Developer's Guide To The Galaxy No.10Marco Tabor
The community-driven, non-commercial, free handbook about mobile technologies. Learn everything about the differences between the platforms, cross-platform approaches and key topics like how to implement NFC, security or haptics in mobile apps.
If you want the book as a hardcopy or want to get involved as a writer or sponsor, write to developers@enough.de
Mobile Developer's Guide To The Galaxy Vol.7Marco Tabor
The 7th edition of the Mobile Developer´s Guide To the Galaxy has been presented on the Mobile World Congress 2011. On 160 pages, it gives an updated overview on mobile technologies, the differences between the numerous mobile platforms and possible development approaches. The new edition contains new chapters about app development for BlackBerry, about cross-platform development and about how to create accessible mobile software.
It is an open project hosted and coordinated by the German product and service provider Enough Software. Currently 17 experts from the mobile ecosystem contributed their know how, everyone is invited to join.
Send your feedback and input directly to: developers@enough.de
Mobile Developer's Guide To The Galaxy 12th EditionMarco Tabor
The latest edition of the popular free book about mobile technologies, aimed at developers and decision makers alike.
Over 20 experts from the mobile community introduce you to topics like app prototyping, developing Android/ iOS/ Java ME/ BlackBerry and Windows Phone apps, cross-platform development, mobile app analytics, accessibility in mobile apps, LBS, augmented reality, app monetization, app stores and a lot more.
This book has been distributed on barcamps, conferences, industry events and at universities worldwide- over 50,000 hardcopies have been printed until today. It's probably the most up-to-date publication you will find.
This presentation was for the Cambridge Wireless “Open Source - free lunch?” Software SIG event on 25th February 2009. The event aimed to explore the world of mobile open source software development and to challenge the arising issues from this debate.
TotalCross helps developers to create for more devices than any other platform in the world, not only mobile and desktop but also embedded devices like Raspberry Pi, Toradex and more. In the webinar we show news about our technology and plans for 2020. #devfirst
Mobile Developer's Guide To The Galaxy No.10Marco Tabor
The community-driven, non-commercial, free handbook about mobile technologies. Learn everything about the differences between the platforms, cross-platform approaches and key topics like how to implement NFC, security or haptics in mobile apps.
If you want the book as a hardcopy or want to get involved as a writer or sponsor, write to developers@enough.de
Mobile Developer's Guide To The Galaxy Vol.7Marco Tabor
The 7th edition of the Mobile Developer´s Guide To the Galaxy has been presented on the Mobile World Congress 2011. On 160 pages, it gives an updated overview on mobile technologies, the differences between the numerous mobile platforms and possible development approaches. The new edition contains new chapters about app development for BlackBerry, about cross-platform development and about how to create accessible mobile software.
It is an open project hosted and coordinated by the German product and service provider Enough Software. Currently 17 experts from the mobile ecosystem contributed their know how, everyone is invited to join.
Send your feedback and input directly to: developers@enough.de
Mobile Developer's Guide To The Galaxy 12th EditionMarco Tabor
The latest edition of the popular free book about mobile technologies, aimed at developers and decision makers alike.
Over 20 experts from the mobile community introduce you to topics like app prototyping, developing Android/ iOS/ Java ME/ BlackBerry and Windows Phone apps, cross-platform development, mobile app analytics, accessibility in mobile apps, LBS, augmented reality, app monetization, app stores and a lot more.
This book has been distributed on barcamps, conferences, industry events and at universities worldwide- over 50,000 hardcopies have been printed until today. It's probably the most up-to-date publication you will find.
This presentation was for the Cambridge Wireless “Open Source - free lunch?” Software SIG event on 25th February 2009. The event aimed to explore the world of mobile open source software development and to challenge the arising issues from this debate.
Developers Guide To The Galaxy 8th editionMarco Tabor
Completely updated and extended edition of this non-commercial overview on mobile technologies and development approaches. Helpful for developers and decision makers without technical background.
Mobile Developer's Guide To The Galaxy No. 9Marco Tabor
This non-commercial brochure by the German company Enough Software (www.enough.de) provides an overview on the different mobile technologies and platforms. Almost 20 writers contributed their know-how and outline their views on the pros and cons of different operation systems and development approaches. Together with the Wireless Industry Partnership (WIP), we started this project in 2009. The current 9th edition has been presented in October 2011 and consists of 170 pages.
Please send your feedback and input directly to developers@enough.de
Use the same address if your company would like to sponsor upcoming editions.
In case you would like to get hardcopies of the guide, we will be happy to send them over to you. You would just need to pay us the postage and packaging.
This document shows the important highlights from Mobile World Congress 2016 (MWC 2016).
The show hosted the new flagship mobile phones like Samsung Galaxy S7 or LG G5 as well as new tablets like Huawei Matebook…
In this document, I wanted to show you some interesting highlights from the show rather than taking you through these new devices.
Mobile Developer's Guide To The Galaxy 11th editionMarco Tabor
The 11th edition of Enough Software's popular handbook about mobile technologies- for developers and decision makers. 240 pages packed with valuable and objective information about all mobile platforms, different programming paradigms, monetization of apps, accessibility and a lot more.
All you need to get started in the mobile world and still a lot to learn if you're a veteran.
Cross Platform Development Using Fluttervivatechijri
Today the development of cross-platform mobile application has under the state of compromise. The developers are not willing to choose an alternative of either building the similar app many times for many operating systems or to accept a lowest common denominator and optimal solution that will going to trade the native speed, accuracy for portability. The Flutter is an open-source SDK for creating high-performance, high fidelity mobile apps for the development of iOS and Android. Few significant features of flutter are - Just-in-time compilation (JIT), Ahead- of-time compilation (AOT compilation) into a native (system-dependent) machine code so that the resulting binary file can execute natively. The Flutter’s hot reload functionality helps us to understand quickly and easily experiment, build UIs, add features, and fix bugs. Hot reload works by injecting updated source code files into the running Dart Virtual Machine (VM). With the help of Flutter, we believe that we would be having a solution that gives us the best of both worlds: hardware accelerated graphics and UI, powered by native ARM code, targeting both popular mobile operating systems.
Are you in search of computer training in Ambala?
Now your search ends here... Batra Computer Centre provides you the best IT training in Ambala Cantt. We offers you many other courses such as Basic computer course , C, C++, Web designing , Web Developnent, SEO etc.
Developers Guide To The Galaxy 8th editionMarco Tabor
Completely updated and extended edition of this non-commercial overview on mobile technologies and development approaches. Helpful for developers and decision makers without technical background.
Mobile Developer's Guide To The Galaxy No. 9Marco Tabor
This non-commercial brochure by the German company Enough Software (www.enough.de) provides an overview on the different mobile technologies and platforms. Almost 20 writers contributed their know-how and outline their views on the pros and cons of different operation systems and development approaches. Together with the Wireless Industry Partnership (WIP), we started this project in 2009. The current 9th edition has been presented in October 2011 and consists of 170 pages.
Please send your feedback and input directly to developers@enough.de
Use the same address if your company would like to sponsor upcoming editions.
In case you would like to get hardcopies of the guide, we will be happy to send them over to you. You would just need to pay us the postage and packaging.
This document shows the important highlights from Mobile World Congress 2016 (MWC 2016).
The show hosted the new flagship mobile phones like Samsung Galaxy S7 or LG G5 as well as new tablets like Huawei Matebook…
In this document, I wanted to show you some interesting highlights from the show rather than taking you through these new devices.
Mobile Developer's Guide To The Galaxy 11th editionMarco Tabor
The 11th edition of Enough Software's popular handbook about mobile technologies- for developers and decision makers. 240 pages packed with valuable and objective information about all mobile platforms, different programming paradigms, monetization of apps, accessibility and a lot more.
All you need to get started in the mobile world and still a lot to learn if you're a veteran.
Cross Platform Development Using Fluttervivatechijri
Today the development of cross-platform mobile application has under the state of compromise. The developers are not willing to choose an alternative of either building the similar app many times for many operating systems or to accept a lowest common denominator and optimal solution that will going to trade the native speed, accuracy for portability. The Flutter is an open-source SDK for creating high-performance, high fidelity mobile apps for the development of iOS and Android. Few significant features of flutter are - Just-in-time compilation (JIT), Ahead- of-time compilation (AOT compilation) into a native (system-dependent) machine code so that the resulting binary file can execute natively. The Flutter’s hot reload functionality helps us to understand quickly and easily experiment, build UIs, add features, and fix bugs. Hot reload works by injecting updated source code files into the running Dart Virtual Machine (VM). With the help of Flutter, we believe that we would be having a solution that gives us the best of both worlds: hardware accelerated graphics and UI, powered by native ARM code, targeting both popular mobile operating systems.
Are you in search of computer training in Ambala?
Now your search ends here... Batra Computer Centre provides you the best IT training in Ambala Cantt. We offers you many other courses such as Basic computer course , C, C++, Web designing , Web Developnent, SEO etc.
Android is an operating system for mobile devices such as smart phones and tablet computers. It is developed by the Open Handset Alliance led by Google. Android, Inc. was founded in Palo Alto, California, United States in October, 2003 by Andy Rubin, Rich Miner, Nick Sears, and Chris White to develop, in Rubin\'s words "...smarter mobile devices that are more aware of its owner\'s location and preferences".
A presentation about Android, Google's Operating System offering in the space of Mobiles.
Slide focuses on technicalities of the OS and is introductory only.
Android is a mobile operating system based on a modified version of the Linux kernel and other open-source software, designed primarily for touchscreen mobile devices such as smartphones and tablets.
Mobile World Congress 2013: A report from the floorDMI
Insights from MWC 2013, the worlds biggest mobile event – coverage of the latest mobile devices and operating systems as well as trends in mobile retail,mobile payments and enterprise mobility.
Mobile Developers Guide To The Galaxy Vol.6Marco Tabor
The latest updated edition of Enough Software`s Guide to mobile platforms. Useful for application developers as well as for decision makers wanting to enter the mobile market.
Read other blog posts by the author, Zahid Ghadialy, here: https://communities.cisco.com/people/ZahidGhadialy/content
For more discussions and topics around SP Mobility, please visit our Mobility Community: http://cisco.com/go/mobilitycommunity
This paper outlines the need for traffic matrices and describes how Demand Deduction works. You will learn what a traffic matrix is and how Demand Deduction creates reliable traffic matrices; Demand Deduction as a proven accurate, complete, and useful traffic simulation.
More Information: http://cisco.com/go/quantum
Next-Generation Knowledge Workers: Accelerating the Disruption in Business Mobility White Paper: http://cs.co/6019ZLTv
For more discussions and topics around SP Mobility, please visit our Mobility Community:http://cisco.com/go/mobilitycommunity
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Neuro-symbolic is not enough, we need neuro-*semantic*
Android - to be or not to be?
1. Service Provider Mobility: Android - to be or
not to be?
Posted by David Almstrom Nov 22, 2009
That Android has got a lot of publicity and public endorsement in the US is clear to all of
us but the potential impact that Android can have is probably far beyond what you have
thought. I am therefore posting some of my 'insights' in the subject.
When Andy Rubin left Sidekick and started Android (and acquired by Google), he and his
team did a few things amazingly correct. The first thing they want to do was to embedded
Google services as much as possible; secondly, providing a standardized easy to develop
developer experience that is standardized across devices; and thirdly, provide a nice and
easy UI.
What they did not do was to provide a native SDK, nor any tools to easily modify and change
the UI, nor any backwards compatibility between 1.0, 1.5, 1.6 and 2.0 - as for developers,
it did not matter - they had the Dalvik SDK (which is stable). But the Android team released
most of their code under an open source license (MIT) and that opened up for an unrivaled
deployment from chipset, ODMs, OEMs and even operators.
And to be fair, Android is now the one and only open source package that provides
everything from UI, kernel, sandbox and a bunch of applications that constitutes the basics
of a smartphone. So what has this lead to?! Well, I can't tell you everything as some is
information given in customer confidentiality, but some I can share:
- Mobile phones (Google-certified): HTC, Motorola, LGE, Samsung (though Samsung maybe
not be totally backing it) and SonyEricsson (HTC);
- Operator endorsement from Verizon, T-Mobile, 3 and more on the way. What the OEMs
and ODMs keep hearing is the demand for Android-based devices;
Generated by Jive SBS on 2010-05-25-06:00
1
2. Service Provider Mobility: Android - to be or not to be?
- Mobile phones (non-Google): China Mobile's oPhone (w Dopod, LGE, Dell and other
producing phone); a number of shanzhai phones; virtually all ODMs (to mention a few:
Yuhuatel, Pegatron, Quanta, etc.);
- Smartbooks: not supported by Google, but the ODMs and some OEMs are in full
development of Android-based Netbooks, driven by operator demand. I have seen demos
based on Qualcomm Snapdragon and Freescale iMX.51 done by ODMs in Taiwan;
- STB: I have been shown a few various reference designs by customer who has been using
Android;
- In-Car Infotainment systems: One of the biggest Chinese car manufacturers is developing
an Android-based solution (want phone capabilities); and
- Chipsets: nearly all chipset manufacturers have a demo with Android (Freescale,
Qualcomm, TI, Marvell, etc. - even MIPS now).
At the ARM symposium that I attended in Taipei and Hsinchu last week, ARM itself had a
number of speeches to show how to innovate and develop with ARM and Android. Apart
from our Qt-demo and Movial's, a few were Windows Mobile and the rest was just Android.
In Japan, the in-official Android community is huge - more than 2,000 open source
developers (and growing), compared with some 50-100 in KDE.
I was speaking at Web Wednesday in Beijing the same week in order to share my
experience with open source business models. And most of the developers there were
totally ignoring Nokia but a few them was really in favor of Android. The perception of
Android's strengthen a position, is in my opinion, greatly over-rated, as there are clear signs
already of fragmentation (and thus developers will not have such an easy life) but perception
rules!
What drives this? For any ODM or OEM who wants to e.g. use an ARM-based chipset
to drive down cost and to build a device quickly (partly being able to show a demo to a
customer to be able to sell in the design), there are a number of things to look out for:
Generated by Jive SBS on 2010-05-25-06:00
2
3. Service Provider Mobility: Android - to be or not to be?
- free open-source solution means no budget spending and lengthy contract negotiations
with supplier. I.e. easy to start the project and low/minimum risk
- avoid plumming that do not add any value. In the plumming, we have kernel porting,
driver development, media-framework (some value in optimizing and performance), back-
end features (SQL, UI toolkits, etc.), basic applications (such email, browser, dialer) and a
sandbox model for installing 3rd party applications
- 3rd party application development model for developing and deploying applications on
devices but also making it easy for the OEM/ODM themselves to add/develop pre-installed
applications. The Java language makes it fairly easy for anyone to develop apps given that
large existing Java developer community.
So what could go wrong? What could stop the Android and make him rust. There are
hurdles and deploying on non-ARM chipsets are one; memory consumption can make the
devices too expensive (beyond mobile); difficult to develop and customize the UI (important
once the screen is not standard screen) and of course, consumer uptake. Still there are no
evidence of real consumer uptake and the next year stand to prove the case.
There are also some large developer houses that questions the viability of Android and
ability for 3rd parties to make some serious money. Gameloft recently announced cutbacks
of Android apps development. A quote: "We have significantly cut our investment in Android
platform, just like ... many others," Gameloft finance director Alexandre de Rochefort said at
an investor conference.
Android could also fragment itself to non-importance with its open-source model and
non-backward compatibility in the framework and Native controllers. It could become
the preferred choice for building anything but would be limited to UI and some on-device
preloaded applications and a browser and not much more beyond mobile phone. Also
Chromium OS may divert attention and given that ChromeOS is built upon Canonical's
Linux distro, there are also chances that we can easier get Qt and CWRT running on those
devices. But I fear that Google in true non-open source spirit and its aim to rule the world
will limit OEMs/ODMs if they want Google services preloaded on their devices
Generated by Jive SBS on 2010-05-25-06:00
3
4. Service Provider Mobility: Android - to be or not to be?
Alternatives to Android? Moblin maybe, but that is x86-based and not open to non-Intel
chipsets (GPL only otherwise) which really limits uptake
And where is Maemo? Should that have been one of the options for any ODM? Well,
probably but it seems too complicated to build a device based on ODM.
SonyEricsson provides an alternative view on how to provide a developer experience:
And this is also well in-line with Nokia's push for the WebRuntimes that is on S60 devices
and also in some of the S40 and also Maemo. Similar for PalmPre and this is also aligned a
bit with Chromium OS. Webapps is the future?
927 Views Tags: qt, android, websdk
Nov 24, 2009 12:17 PM Robert Synnestvedt
Thanks for the insight David. A few things come to mind that lead me to believe that there
will not be universal Android adoption for quite awhile, if ever ...
First if we look at current Mobile OS market share for SDK and trained professionals building
apps and systems, we find Google Android comes in last place:
Generated by Jive SBS on 2010-05-25-06:00
4
5. Service Provider Mobility: Android - to be or not to be?
* Nokia Symbian
* RIM Blackberry
* Apple OS X for MACs, iPhones, tablets etc.
* Microsoft
* Linux
* Google Android
What would drive these communities to abandon what they've invested in to jump onto
Android? In fact don't some of these communities view Android as "evil" (developers can
offer pretty strong opinions ;-)
Nov 24, 2009 10:14 PM David Almstrom Robert Synnestvedt in response to
Robert,
you highlight an important aspect. Developers will normally go for the most deployed
devices in the market and develop applications. However, it seems that Nokia (whom I am
working for) has managed to break that paradigm - particularly in the US.
If you ask what developers are developing for, you would probably see something like this:
1. iPhone/iPods - everyone
2. Android as the second platform for most
3. RIM or MS
A lot of the US-based developers will not even consider Nokia/Symbian as its developer
offering currently is flawed. There are a lot of works in progress from both Nokia and
Symbian Foundation to fix that of course and I believe it will improve.
Generated by Jive SBS on 2010-05-25-06:00
5
6. Service Provider Mobility: Android - to be or not to be?
But it is also regional. In China, S60v3 is the first platform that developers will develop for
and then maybe even S60v2 before considering MTK and/or Java.
But from a device manufacturer, the promises of Android makes statement where Android
now is in the last place obsolete. However, there is a very obvious concern that due to the
openness of Android and that Google is not able to enforce compatibility between platforms
that the Android developer market will be highly fragmented. Wired posted an interesting
article sometime ago.
And that can give Nokia an edge in consolidating the developer market around 100M+
devices yearly.
Nov 25, 2009 2:11 PM Robert Synnestvedt David Almstrom in response to
Android ... to be or not to be? That is the question ... market share perspective is much
smaller than iPhone after first year, but is trending up ... but I see Nokia as so powerful in
this space it's hard for me to get head around idea that Android could be dominant. Do you
see it becoming "The" dominant Mobile device OS? Would Nokia let that happen? ;-)
The blurring of Mobile Internet application use cases between smartphones, MIDs, laptops
etc. makes this all the more fascinating to me.
Google offering Android on the one hand, then building their own Google Phone (will all
Android device manufacturers truly get the same just-in-time access to everything Android
has to offer? Will Google Phone have leading edge to updates?), while supplying Chrome
for "bigger?" devices ... doesn't sound like something that exudes great confidence for
developers to race after. But then again, as you state, "perception rules"
And what of App Stores? Are they destined to remain client based? Or will there be
"emulators" to run your previously purchased apps on a new device?
Generated by Jive SBS on 2010-05-25-06:00
6
7. Service Provider Mobility: Android - to be or not to be?
Finally, what of trending to "The Cloud" ... makes me wonder if the drive to save even
more battery life and further reduce device costs will influence the "smart" phones toward a
destiny of dumb TTY terminals linked into intelligent clouds ;-)
Whatever the final destination, its great to have insight from people like you in our
community, driving and deliberating where to take this ... I bet part of our "discusion" should
go into Discusion ... and something tells me that regardless of which OS "wins", having a
reliable and ubiquitous network connection in between these Mobile Internet devices will
remain pretty important
Nov 26, 2009 12:19 AM David Almstrom Robert Synnestvedt in response to
personally, I think there will always be a number of platforms, a number of choices - as
people are different and have different needs.
If not, we would all be on Microsoft PCs by now and we are not. Nokia will of course not
sit quiet and let Google take over and the alliance lately with Microsoft can prove to be
powerful.
The Cloud fits some people - but the unreliability of network access and tied with the cost of
bandwidth (there is a cost for that) will push for more than cloud-based services/computing.
There will always be low-end vs high-end, simple vs full-features, faster vs more complexed,
etc.
Who wants the dumb terminal back?
Dec 1, 2009 12:10 AM Mike Demler David Almstrom in response to
Very interesting thread. I just finished writing a report on the "Android Invasion" that has
occured here in the U.S., starting just before CTIA Wireless in October and continuing
non-stop ever since. A lot of very good technical points are raised in this discussion, but I
think my perspective is somewhat different since my point-of-view is mostly focused on the
business implications.
Here are just a few of my opinions/observations:
Generated by Jive SBS on 2010-05-25-06:00
7
8. Service Provider Mobility: Android - to be or not to be?
1. Very simply - Google's goal with Android in smartphones is to do on the mobile
internet what they have done already to the desktop. Individually, the basic
components (browser, search engine, email, etc.) built on top of the OS are
secondary to the end result that is achieved by their integration: a synergistic
platform that facilitates commerce. (See the AdMob purchase). On the desktop it
was a matter of integrating (mostly) into Windows. Not so on the mobile handset..
hence the need for Android.
2. It's a numbers game. The U.S. wireless operators that are currently supporting
Android (Verizon, Sprint and T-Mobile) account for more than 170M cell phone
users. That is more than 2X the total available market addressed by iPhone-
dependent AT&T. I'm not sure what David means by fragmentation, but apps
developers can't help but be drawn to redirecting their efforts to that larger market
where one app hits more phones and more target users for the same amount of
effort. Verizon's $100M DROID campaign is backing them up, along with all the
other carrier's efforts. Apple is very profitable, but it is repeating the same closed-
platform philosophy that it executed on the desktop... and we know how that worked
out.
3. When I see open source I read ecosystem. Nokia may have a strong Symbian
ecosystem in Europe, but it has near-zero presence in the U.S., and make no
mistake.. the U.S. drives the smartphone business. The ecosystem of the Open
Handset Alliance spans semiconductors, to design tools, to application software,
to CE manufacturers, to service providers. If that is the result of being "open" so be
it. The bottom line is that this represents a very formidable ecosystem that Apple's
closed system can't match, and neither can Nokia. Nokia should integrate Android
into their Qt porting framework, or risk losing any chance of gaining market share in
the U.S.
4. Android will be in set-top boxes and other CE devices, as the convergence of the
internet and digital media penetrates further into the digital living room.
5. Don't forget Google's investment in Clearwire. Look for a WiMax Android
smartphone, if not 2010, definitely in 2011.
-Mike Demler
Dec 1, 2009 11:10 PM Robert Synnestvedt Mike Demler in response to
I saw Apple's "closed" offer more as a gateway for the OS X developer community to easily
port apps into the rapidly expanding Mobile Internet community. App store volume suggests
they got that part right .. iPhone user interface + application combo offered the "Wow" factor
to draw a crowd
Generated by Jive SBS on 2010-05-25-06:00
8
9. Service Provider Mobility: Android - to be or not to be?
We just busted through Black Friday in the States ... it'll be interesting to see how the
holidays (and Verizon $100M ad campaign!) helps drive Android sales ...
Apple has always had a crowd willing to pay a premium for a small part of the overall
market ... Google draws a crowd that says Internet is free ... it'll be interesting to see what
"revenue sharing" models work out best between subscribers, operators, and the droid eco-
system
Dec 2, 2009 3:34 AM David Almstrom Robert Synnestvedt in response to
@Mike, with fragmentation I mean that the single app no longer can run on any Android
device as OEMs have started to fork Android of various reason and it is difficult for Google's
Android to enforce full compatibility. E.g. GPS and Camera integration are handware
dependent and in order to make it work, the APIs may change.
It is quite interesting how, due to Apple, US regain the edge in the mobile market after
losing in the early 90s to Europe. In the early 00s, US mobile market was a joke but it has
changed. But 170M cell phone users is not that much. China adds 80-100M cell phone users
yearly. India as well (though 80% is low-end phones).
The chinese operators are all forking Android to O-phone (CMCC), U-Phone (Unicom) and
C-phone (Telecom) - all on Android, all on their own SDKs and modifications. Here one
Android app will for sure not run on the other platforms. And Nokia will probably the uniting
factor here.
But the idea of Qt supporting Android is not new and I really think that we need to take Qt to
Android (remember, I work for Nokia) but as good as it sounds, it is not as straightforward.
Ideas more than happily received.
Dec 2, 2009 10:39 AM Mike Demler David Almstrom in response to
Hi David,
I wonder how severe the issue of fragmentation of the Android OS is. I can see backward
compatibility being an issue, but is the basic foundation of the OS revs that Google releases
even changeable by developers? The developer is responsible for testing hardware
Generated by Jive SBS on 2010-05-25-06:00
9
10. Service Provider Mobility: Android - to be or not to be?
dependencies. There are numerous emulators available, which is a topic I cover in my
recently published report on "The Android Invasion".
A bad (i.e. incompatible) app is a bad app, and they will exist regardless of the platform,
iPhone or Android. As smartphones are just portable computers, it follows that some of the
same problems we see with hardware dependencies on the desktop will occur. However,
I don't see a problem with developing apps that are targeted at specific hardware as long
as that is specified, nor do I see a problem with creating regional variations. This sort of
"fragmentation" just creates more opportunities.
I realize that 170M subscribers is a small fraction of the 2B worldwide, but of course I was
directing that point at U.S. developers - just to provide some perspective relating to the "gold
rush" to iPhone app development. Android opportunities will dwarf iPhone because of the
"fragmentation", or perhaps more accurately - "diffusion of innovation", just as has occured
with the numerous variations of Windows OS configurations that dominate the PC market.
I am curious about your comment that "Nokia will probably the uniting factor". Can you say
more about that?
Great discussion..
Mike
Dec 2, 2009 10:51 AM David Almstrom Mike Demler in response to
it is difficult now to say how severe the fragmentation will be. It is more likely to happen
in the open-source device ODM/OEMs (STB to MID to Netbooks to whatever) rather than
the mobile phones. But even in the mobile phones, the OEMs are enhancing Android and
when they do, they add features that requires specific SDKs, etc. etc. and immediately, the
developers that targets the 170M potential Android users ends up to have to target 5-10
different phones with 100K-2/3M units.
At Nokia we have learnt that lesson the hard way. We managed to break the paradigm that
developers target the most deployed platform. And by all numbers, Nokia has deployed
Generated by Jive SBS on 2010-05-25-06:00
10
11. Service Provider Mobility: Android - to be or not to be?
more smartphones combined than all others but with a number of platforms where binary
compatibility have been broken repeatedly.
wrt my comment about Nokia being the uniting factor, I was referring more to China as the
market, where if the three operators post their own non-compatible Android SDKs, Nokia
with our dominating market share can get the developers to develop for Qt/Webruntime/Java
on Nokia devices and be sure that it will be able to run on all operator's handsets (if the user
has a Nokia device).
Once Qt is one of the preferred developer platforms, the developers can also port (or rather
deploy) their apps on non-Nokia devices. E.g. Windows Mobile phones, Samsung Symbian
phones, Asus Netbooks (Linux/Windows), TV/STB running Qt. and so on.
Generated by Jive SBS on 2010-05-25-06:00
11