Autoren:
Roland Gülle, Sevenval GmbH
Robert Virkus, Enough Software
Thibaut Rouffineau, WIP
Brochure which deals with the typical questions that come up during the mobile development process.
This document provides a guide to cross-platform mobile app development. It discusses how cross-platform apps can save money by requiring less development costs and reaching a wider audience. Native apps require separate development for each platform, while cross-platform uses one codebase. Popular cross-platform tools include React Native, Xamarin, Ionic, and Flutter. Factors like costs, time savings, and audience reach make cross-platform development beneficial for many businesses.
The document discusses options for cross-platform mobile development, including mobile web, native apps, native wrappers, interpreted apps, and cross-compiled apps. It focuses on using Xamarin tools to build cross-platform apps using C# that can target both Android and iOS platforms. Xamarin allows developers to share most of their code across platforms while still delivering native experiences. The document includes demonstrations of building an app with Xamarin and considerations for selecting mobile development tools.
The document discusses beginning BlackBerry application development. It covers choosing an SDK version and development environment. The SDK version is tied to the BlackBerry OS version, and applications developed for an older SDK may not utilize features of newer OS versions. The document recommends using the Eclipse integrated development environment with the BlackBerry plug-in, as it provides developer-friendly features and leverages the Eclipse platform. A minimum target of BlackBerry OS 5.0 is suggested to cover most devices and support in the BlackBerry App World.
LUMIA APP LABS: WINDOWS PHONE 8 FOR NOKIA DEVELOPERS
These webinar slides introduce what’s new in Microsoft Windows Phone 8, with an emphasis on those features that are sure to excite Nokia developers the most. Whether you’re completely new to Windows Phone or you have Windows Phone applications already on the market, you’ll see how Windows Phone 8 offers new opportunities. We’ll cover new APIs and technologies, enablers for better app monetisation, and cross-platform portability.
[Whitepaper] an overview of ibm mobile first platform
The document provides an overview of the IBM MobileFirst Platform for building, testing, integrating, deploying and managing mobile applications. It discusses the following key points:
1. The MobileFirst Platform consists of Foundation for development, App Scanning for detecting vulnerabilities, and Quality Assurance for collecting feedback.
2. It supports various development approaches from native to hybrid to web and provides tools like Studio IDE and CLI for efficient development.
3. Features like automated testing, centralized builds, and runtime skins help optimize the development process.
The document discusses various approaches to mobile app development including native, mobile web, hybrid, cross-compiled, and virtual machine-based apps. It analyzes the advantages and disadvantages of each approach based on criteria like user experience, portability, time to market, and maintenance. While native apps provide the best user experience, mobile web apps have better portability across platforms. The document recommends evaluating key business parameters and priorities to determine the best development strategy for an organization's needs.
Nashua Cloud .NET User Group - Basic WP8 App Dev With XAML and C#, April 2013
This document provides a 3 sentence summary of the Basic Windows Phone 8 Application Development with XAML & C# document:
The document outlines the core concepts and structure for developing basic applications for Windows Phone 8 using XAML and C#, including an overview of pages, controls, navigation, and the application lifecycle. It also covers important UI elements like the LongListSelector, Pivot, and Panorama controls as well as data storage options and the application bar.
Are MEAPs the answer to all our problems with mobile device development and deployment, or simply a recurring fallacy from what we saw in the mid-late 90's with cross-platform development for PC, Mac, Unix, and the Web? In this presentation I take an objective view on the category, highlight potential issues, and offer thoughts on an alternative approach.
Where Do Cross-Platform App Frameworks Stand in 2020?
Cross-platform app frameworks allow developers to write code once and deploy apps to both Android and iOS, reducing costs and time to market. The top frameworks are Xamarin, React Native, Flutter, PhoneGap, and Ionic. Xamarin uses C# but can be expensive for enterprises. React Native is popular but lacks platform consistency. Flutter creates native-like apps quickly but lacks TV support. PhoneGap uses web technologies but has performance issues. Ionic is similar to AngularJS and allows progressive web apps. The best framework depends on the specific app needs and goals.
Greane Tree Technology CTO Joseph Payette gave our latest “Lunch & Learn” presentation. With the number of tools and frameworks for cross platform mobile application development increasing every year, it can be a challenge to determine the best fit technology for a mobile project. All of these tools and frameworks have their advantages and disadvantages, as they leverage different mechanisms for abstracting differences across mobile devices in an effort to provide a single platform for rapid application development. To bring order to the various options at hand, Joe reviewed mobile application architectures (native, hybrid, and HTML5), and explored and compared a few hybrid tools and frameworks, namely PhoneGap (www.phonegap.com), Appcelerator (www.appcelerator.com), and MoSync (www.mosync.com). Joe’s mobile application development presentation includes sample code for these three tools and frameworks.
The Lunch and Learn series is a regular event where we discuss topics of interest to our projects and clients. Last month, Chad Calhoun explored Git Interactive Techniques.
AIR & Printing is a talk made during SOTR 2010 in London.
During this event I talked on how to work offline with AIR to create PDF in runtime directly with Actionscript 3 without using any other technology
IRJET- Cross Platform User Compatible System with Specific Application
1. The document discusses cross-platform mobile application development which allows apps to run on multiple operating systems like Android and iOS.
2. It explains different types of cross-platform apps like web, hybrid, and interpreted apps. Cross-platform tools allow developers to write code once and deploy it to different platforms.
3. The document analyzes advantages of cross-platform apps like reusable code, reduced development time and costs since code only needs to be written and tested once rather than for each platform.
Top 4 Cross Platform tools for Mobile App Development
Scope of Cross Platform App Development is bright as developers and engineers find it easy and interesting to use a single code base to compile and deploy their app on all major mobile platforms. Top 4 Cross Platform Development tools are discussed here in the presentation, with few of their major pros and cons:
Cross platform mobile app development tools review
The document discusses various cross-platform mobile app development frameworks. It describes frameworks that use web technologies like HTML5, CSS, and JavaScript to build apps that are portable across platforms (e.g. PhoneGap, Rhodes). It also discusses frameworks that use cross-compilation to build truly native mobile apps from a common codebase (e.g. Xamarin, Appcelerator). The document provides brief overviews of popular frameworks like Sencha Touch, Appcelerator, and MoSync, outlining their pros, cons, and capabilities.
This document discusses mobile application development. It covers the importance of mobile apps, different development choices like native, hybrid and mobile web apps, and factors to consider from the perspectives of users, developers and businesses. The key platforms are discussed along with their market shares. Native apps can access all device APIs but must be developed for each platform separately. Hybrid apps combine web technologies with native wrappers for a cross-platform experience. Mobile web apps run in browsers but have limited device access.
Bashyam Spiro LLP - Hot Topics In Employment Based Immigration
The document discusses key topics in employment-based immigration, including PERM labor certification process reforms, options for cases filed under the old process, H-1B visa issues, and green card processing times. Under the new PERM system, employers must conduct recruitment before applying and offer the prevailing wage. Pending cases were transferred to Backlog Reduction Centers with uncertain processing times. Converting an old case to PERM risks losing priority dates or the ability to extend H-1B status beyond six years. Faster green card processing is occurring at some service centers.
Bashyam Spiro LLP - U.S. Citizenship And Family Immigration
There are two primary ways to become a US citizen: by birth in the US or by naturalization. To naturalize, one must generally be a lawful permanent resident for 5 years, meet residency requirements, demonstrate good moral character, pass English and civics tests, and take the Oath of Allegiance. US citizens can then sponsor relatives like spouses, children, and parents to become lawful permanent residents. However, the process involves forms, visas, background checks, and overcoming potential issues like proving a marriage is valid.
Bashyam Spiro LLP - Beyond Six Years On H-1B Status
The new law allows H-1B status to be extended beyond the typical 6-year maximum if over 365 days have passed since filing an application for labor certification or an employment-based immigrant petition. Extensions will be granted in one-year increments until a final decision is made on the application for permanent residency. Family members are also eligible for extensions of their H-4 status as long as the principal H-1B recipient receives an extension. However, family members cannot continue working under their own H-1B status past 6 years unless independently eligible.
Bashyam Spiro Immigration Law Group_AC21 Portability
Are you currently going through the employment-based residency process and wonder if changing jobs will impact your application? Have you heard about AC21 portability and want to learn more about how it can impact your case? If so, this informative Webinar is for you! During this webinar Bashyam Spiro LLP’s immigration attorneys will explain how changing jobs can impact a residency application, and what steps one must take if changing jobs when the application is still pending.
A panel discussion was held on blogging in Latin America featuring moderator Erin De Santiago and panelists Dorian Nunez, Kelly McLaughlin, and David Lee. The panelists, who blog about various Latin American countries, discussed the benefits and drawbacks of blogging in the region, social media trends, freelancing opportunities, issues encountered, and the future of travel blogging in Latin America. The panel then took questions from the audience.
Dealing with haters, and flamers and trolls veronica james
The document discusses strategies for dealing with hostile comments ("haters, flamers and trolls") on blogs and websites. It defines internet trolls and provides an example of a personal troll. It advises blog owners to visualize their troll, find their own voice by defining their values and audience, and distinguish between disruptive trolls and constructive "garden gnomes". The document also recommends harnessing supporters by sharing hostile comments and writing follow-up posts.
The document reports on mobile device and browser trends from November 2014 data from Sevenval. The top three mobile devices by traffic were the iPhone 5, Samsung Galaxy S3, and Samsung Galaxy S4. The most popular browsers were Apple Mobile Safari, Google Chrome for Android, and the Android built-in browser. The dominant operating systems were Open Handset Alliance (Android) at 61% and Apple at 35%. It notes that there are over 7,000 different devices accessing mobile websites and that fragmentation in the mobile space is ongoing.
This powerpoint presentation explains the Diversity Visa Lottery Program that provides 50,000 green cards for applicants around the world in a random selection process. We review the criteria required to qualify for the lottery program for immigrants interested in applying for US permanent residency through the Diversity Visa Program.
TBEX15 North America Fort Lauderdale Lauren & Kenin Bassart
This document outlines a 7-step process for pitching sales opportunities to potential brand and destination partners: 1) Prepare by defining your brand and audience; 2) Make first contact; 3) Qualify partners by learning their needs; 4) Ask key questions to customize solutions; 5) Make the pitch by outlining offerings; 6) Negotiate to get approval, addressing any objections; 7) Fulfill commitments and maintain the relationship for future opportunities. The goal is to build long-term, mutually beneficial relationships through strategic selling and partnership.
Mobile Developer's Guide To The Galaxy, 5th edition
This document provides an overview of different mobile application development environments, including native applications, J2ME, Flash Lite, BREW, widgets, and mobile web. It describes the programming languages, requirements, and considerations for each environment. The document aims to help developers choose the best environment for realizing their mobile application ideas.
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
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.
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.
The document discusses several mobile platforms and their development environments. It summarizes Jalimo, an open source project that aims to bring full Java support to mobile Linux platforms like Maemo and OpenMoko. Jalimo uses various Java runtimes and toolkits to allow desktop Java applications and APIs to run on these platforms. It utilizes tools like OpenEmbedded and Maven for building and packaging Java applications to run on mobile Linux devices.
This presentation has been developed in the context of the Mobile Applications Development course, DISIM, University of L'Aquila (Italy), Spring 2015.
http://www.ivanomalavolta.com
KonyOne is a mobile development platform that allows developers to build cross-platform native and web applications using a low-code approach. The document discusses installing KonyOne and using its development tools to define a mobile application that retrieves and displays data from a web service. Key aspects noted include the familiar Eclipse-based IDE, forms-based design, extensive support for integrating web services, and the ability to deploy applications as native apps or mobile web apps across multiple platforms. Overall, the author found that KonyOne reduces the amount of code required compared to traditional approaches, while still producing high-quality cross-platform mobile applications.
Mobile application development has grown significantly in recent years with the rise of smartphones. There are many mobile operating systems and platforms that each have their own approach. Java ME and BREW are virtual environments that provide a common development platform but have limitations. Symbian and S60 are mature operating systems that dominate the market but have complex development environments. The iPhone platform is very popular but tightly controlled by Apple. Android provides an open alternative with a full software stack based on an optimized Java virtual machine. It allows for modular application components and uses intents to facilitate interaction. Overall, mobile development remains fragmented but platforms are working to standardize and open up to developers.
This document provides a guide to cross-platform mobile app development. It discusses how cross-platform apps can save money by requiring less development costs and reaching a wider audience. Native apps require separate development for each platform, while cross-platform uses one codebase. Popular cross-platform tools include React Native, Xamarin, Ionic, and Flutter. Factors like costs, time savings, and audience reach make cross-platform development beneficial for many businesses.
The document discusses options for cross-platform mobile development, including mobile web, native apps, native wrappers, interpreted apps, and cross-compiled apps. It focuses on using Xamarin tools to build cross-platform apps using C# that can target both Android and iOS platforms. Xamarin allows developers to share most of their code across platforms while still delivering native experiences. The document includes demonstrations of building an app with Xamarin and considerations for selecting mobile development tools.
The document discusses beginning BlackBerry application development. It covers choosing an SDK version and development environment. The SDK version is tied to the BlackBerry OS version, and applications developed for an older SDK may not utilize features of newer OS versions. The document recommends using the Eclipse integrated development environment with the BlackBerry plug-in, as it provides developer-friendly features and leverages the Eclipse platform. A minimum target of BlackBerry OS 5.0 is suggested to cover most devices and support in the BlackBerry App World.
These webinar slides introduce what’s new in Microsoft Windows Phone 8, with an emphasis on those features that are sure to excite Nokia developers the most. Whether you’re completely new to Windows Phone or you have Windows Phone applications already on the market, you’ll see how Windows Phone 8 offers new opportunities. We’ll cover new APIs and technologies, enablers for better app monetisation, and cross-platform portability.
[Whitepaper] an overview of ibm mobile first platformgule mariam
The document provides an overview of the IBM MobileFirst Platform for building, testing, integrating, deploying and managing mobile applications. It discusses the following key points:
1. The MobileFirst Platform consists of Foundation for development, App Scanning for detecting vulnerabilities, and Quality Assurance for collecting feedback.
2. It supports various development approaches from native to hybrid to web and provides tools like Studio IDE and CLI for efficient development.
3. Features like automated testing, centralized builds, and runtime skins help optimize the development process.
The document discusses various approaches to mobile app development including native, mobile web, hybrid, cross-compiled, and virtual machine-based apps. It analyzes the advantages and disadvantages of each approach based on criteria like user experience, portability, time to market, and maintenance. While native apps provide the best user experience, mobile web apps have better portability across platforms. The document recommends evaluating key business parameters and priorities to determine the best development strategy for an organization's needs.
Nashua Cloud .NET User Group - Basic WP8 App Dev With XAML and C#, April 2013John Garland
This document provides a 3 sentence summary of the Basic Windows Phone 8 Application Development with XAML & C# document:
The document outlines the core concepts and structure for developing basic applications for Windows Phone 8 using XAML and C#, including an overview of pages, controls, navigation, and the application lifecycle. It also covers important UI elements like the LongListSelector, Pivot, and Panorama controls as well as data storage options and the application bar.
Are MEAPs the answer to all our problems with mobile device development and deployment, or simply a recurring fallacy from what we saw in the mid-late 90's with cross-platform development for PC, Mac, Unix, and the Web? In this presentation I take an objective view on the category, highlight potential issues, and offer thoughts on an alternative approach.
Where Do Cross-Platform App Frameworks Stand in 2020?Marianne Harness
Cross-platform app frameworks allow developers to write code once and deploy apps to both Android and iOS, reducing costs and time to market. The top frameworks are Xamarin, React Native, Flutter, PhoneGap, and Ionic. Xamarin uses C# but can be expensive for enterprises. React Native is popular but lacks platform consistency. Flutter creates native-like apps quickly but lacks TV support. PhoneGap uses web technologies but has performance issues. Ionic is similar to AngularJS and allows progressive web apps. The best framework depends on the specific app needs and goals.
Greane Tree Technology CTO Joseph Payette gave our latest “Lunch & Learn” presentation. With the number of tools and frameworks for cross platform mobile application development increasing every year, it can be a challenge to determine the best fit technology for a mobile project. All of these tools and frameworks have their advantages and disadvantages, as they leverage different mechanisms for abstracting differences across mobile devices in an effort to provide a single platform for rapid application development. To bring order to the various options at hand, Joe reviewed mobile application architectures (native, hybrid, and HTML5), and explored and compared a few hybrid tools and frameworks, namely PhoneGap (www.phonegap.com), Appcelerator (www.appcelerator.com), and MoSync (www.mosync.com). Joe’s mobile application development presentation includes sample code for these three tools and frameworks.
The Lunch and Learn series is a regular event where we discuss topics of interest to our projects and clients. Last month, Chad Calhoun explored Git Interactive Techniques.
AIR & Printing is a talk made during SOTR 2010 in London.
During this event I talked on how to work offline with AIR to create PDF in runtime directly with Actionscript 3 without using any other technology
IRJET- Cross Platform User Compatible System with Specific ApplicationIRJET Journal
1. The document discusses cross-platform mobile application development which allows apps to run on multiple operating systems like Android and iOS.
2. It explains different types of cross-platform apps like web, hybrid, and interpreted apps. Cross-platform tools allow developers to write code once and deploy it to different platforms.
3. The document analyzes advantages of cross-platform apps like reusable code, reduced development time and costs since code only needs to be written and tested once rather than for each platform.
Top 4 Cross Platform tools for Mobile App Developmenttechugo
Scope of Cross Platform App Development is bright as developers and engineers find it easy and interesting to use a single code base to compile and deploy their app on all major mobile platforms. Top 4 Cross Platform Development tools are discussed here in the presentation, with few of their major pros and cons:
Cross platform mobile app development tools reviewUday Kothari
The document discusses various cross-platform mobile app development frameworks. It describes frameworks that use web technologies like HTML5, CSS, and JavaScript to build apps that are portable across platforms (e.g. PhoneGap, Rhodes). It also discusses frameworks that use cross-compilation to build truly native mobile apps from a common codebase (e.g. Xamarin, Appcelerator). The document provides brief overviews of popular frameworks like Sencha Touch, Appcelerator, and MoSync, outlining their pros, cons, and capabilities.
Introduction to mobile application developmentChandan Maurya
This document discusses mobile application development. It covers the importance of mobile apps, different development choices like native, hybrid and mobile web apps, and factors to consider from the perspectives of users, developers and businesses. The key platforms are discussed along with their market shares. Native apps can access all device APIs but must be developed for each platform separately. Hybrid apps combine web technologies with native wrappers for a cross-platform experience. Mobile web apps run in browsers but have limited device access.
Bashyam Spiro LLP - Hot Topics In Employment Based Immigrationmbashyam
The document discusses key topics in employment-based immigration, including PERM labor certification process reforms, options for cases filed under the old process, H-1B visa issues, and green card processing times. Under the new PERM system, employers must conduct recruitment before applying and offer the prevailing wage. Pending cases were transferred to Backlog Reduction Centers with uncertain processing times. Converting an old case to PERM risks losing priority dates or the ability to extend H-1B status beyond six years. Faster green card processing is occurring at some service centers.
Bashyam Spiro LLP - U.S. Citizenship And Family Immigrationmbashyam
There are two primary ways to become a US citizen: by birth in the US or by naturalization. To naturalize, one must generally be a lawful permanent resident for 5 years, meet residency requirements, demonstrate good moral character, pass English and civics tests, and take the Oath of Allegiance. US citizens can then sponsor relatives like spouses, children, and parents to become lawful permanent residents. However, the process involves forms, visas, background checks, and overcoming potential issues like proving a marriage is valid.
Bashyam Spiro LLP - Beyond Six Years On H-1B Statusmbashyam
The new law allows H-1B status to be extended beyond the typical 6-year maximum if over 365 days have passed since filing an application for labor certification or an employment-based immigrant petition. Extensions will be granted in one-year increments until a final decision is made on the application for permanent residency. Family members are also eligible for extensions of their H-4 status as long as the principal H-1B recipient receives an extension. However, family members cannot continue working under their own H-1B status past 6 years unless independently eligible.
Bashyam Spiro Immigration Law Group_AC21 Portabilitymbashyam
Are you currently going through the employment-based residency process and wonder if changing jobs will impact your application? Have you heard about AC21 portability and want to learn more about how it can impact your case? If so, this informative Webinar is for you! During this webinar Bashyam Spiro LLP’s immigration attorneys will explain how changing jobs can impact a residency application, and what steps one must take if changing jobs when the application is still pending.
A panel discussion was held on blogging in Latin America featuring moderator Erin De Santiago and panelists Dorian Nunez, Kelly McLaughlin, and David Lee. The panelists, who blog about various Latin American countries, discussed the benefits and drawbacks of blogging in the region, social media trends, freelancing opportunities, issues encountered, and the future of travel blogging in Latin America. The panel then took questions from the audience.
Dealing with haters, and flamers and trolls veronica jamesTBEX
The document discusses strategies for dealing with hostile comments ("haters, flamers and trolls") on blogs and websites. It defines internet trolls and provides an example of a personal troll. It advises blog owners to visualize their troll, find their own voice by defining their values and audience, and distinguish between disruptive trolls and constructive "garden gnomes". The document also recommends harnessing supporters by sharing hostile comments and writing follow-up posts.
The document reports on mobile device and browser trends from November 2014 data from Sevenval. The top three mobile devices by traffic were the iPhone 5, Samsung Galaxy S3, and Samsung Galaxy S4. The most popular browsers were Apple Mobile Safari, Google Chrome for Android, and the Android built-in browser. The dominant operating systems were Open Handset Alliance (Android) at 61% and Apple at 35%. It notes that there are over 7,000 different devices accessing mobile websites and that fragmentation in the mobile space is ongoing.
This powerpoint presentation explains the Diversity Visa Lottery Program that provides 50,000 green cards for applicants around the world in a random selection process. We review the criteria required to qualify for the lottery program for immigrants interested in applying for US permanent residency through the Diversity Visa Program.
TBEX15 North America Fort Lauderdale Lauren & Kenin BassartTBEX
This document outlines a 7-step process for pitching sales opportunities to potential brand and destination partners: 1) Prepare by defining your brand and audience; 2) Make first contact; 3) Qualify partners by learning their needs; 4) Ask key questions to customize solutions; 5) Make the pitch by outlining offerings; 6) Negotiate to get approval, addressing any objections; 7) Fulfill commitments and maintain the relationship for future opportunities. The goal is to build long-term, mutually beneficial relationships through strategic selling and partnership.
Mobile Developer's Guide To The Galaxy, 5th editionMarco Tabor
This document provides an overview of different mobile application development environments, including native applications, J2ME, Flash Lite, BREW, widgets, and mobile web. It describes the programming languages, requirements, and considerations for each environment. The document aims to help developers choose the best environment for realizing their mobile application ideas.
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
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.
The document discusses several mobile platforms and their development environments. It summarizes Jalimo, an open source project that aims to bring full Java support to mobile Linux platforms like Maemo and OpenMoko. Jalimo uses various Java runtimes and toolkits to allow desktop Java applications and APIs to run on these platforms. It utilizes tools like OpenEmbedded and Maven for building and packaging Java applications to run on mobile Linux devices.
The document provides an overview of modern mobile development platforms, trends, and specifics. It discusses the history and major players in mobile development, including Java ME, Symbian, BlackBerry, iOS, and Android. It analyzes the advantages and disadvantages of each platform and provides recommendations on platform selection and development strategies. Key trends mentioned include cross-platform development, mobile advertising, and integration with cloud services.
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
This document discusses factors to consider for mobile software development and porting applications between different mobile platforms. It provides an overview of several popular mobile platforms including BREW, J2ME, Android, iPhone, Blackberry, and Windows Mobile, outlining their key features and limitations. The largest challenge for developers is supporting the many different device configurations given platform fragmentation; while Java enables cross-platform development, differences between devices can prevent true write-once-run-anywhere functionality.
PhoneGap is an open-source mobile development framework that allows building mobile apps using HTML, CSS and JavaScript. It wraps the code in a native container, allowing access to device capabilities like cameras and sensors. Apps are hybrid, using web views instead of native languages. While this allows building once and deploying to multiple platforms, performance may suffer for graphically intensive apps and development time can be longer without native UI controls.
Cross platform mobile development is fastest growing in the market. The basic need for programmers on any platform is compatibility. Here, We presenting most popular tools that will take any developer a long way in creating flexible apps that stand the compality test. For more information, Visit: http://www.greymatterindia.com/mobile-application-development
This document provides an overview of Android application development. It begins with a discussion of mobile phones and applications, and then introduces smartphones and their various platforms like Android, iPhone, and BlackBerry. It highlights reasons for choosing the Android platform, such as its open source nature, large user base, and opportunities for monetization. Technical advantages include using Java and access to device features. The document also outlines various distribution channels for Android apps like the Android Market and 3rd party app stores.
This document discusses the development of hybrid mobile applications. It begins by noting the prevalence of smartphones and the growth of mobile application development. It then discusses the challenges of platform fragmentation for native mobile apps. Web applications are presented as an alternative but are also limited. Hybrid apps, which are native wrappers for web views, combine the best of both approaches. The document uses a sample ASP.NET MVC app to demonstrate how to build a hybrid mobile app with a focus on ASP.NET MVC's suitability as a backend framework.
Introduction to Android Development: Before Getting StartedAhsanul Karim
Android application development seminar focused on getting started. The document provided an overview of mobile and smartphone applications and platforms like Android, discussed why developers should learn the Android platform due to its open source nature, vast opportunities for distribution and business advantages over other platforms. It suggested holding workshops and training programs going forward to help novice developers learn.
Most of the developers use the cross-platform mobile development solutions to develop the mobile
application once and run it on many platforms. Many of these cross-platform solutions are still under
research and development. Also, these solutions are based on different approaches such as Cross-
Compilation approach, Virtual Machine approach, and Web-Based approach. There are many survey
papers about the cross-platform mobile development solutions but they do not include the most recent
tools, including Component-Based approach, Cloud-Based approach, and Merged approach. The main aim
of this paper is helping the researchers to know the most recent approaches and the open research issues.
This paper surveys the existing cross platform mobile development tools, introduces a comprehensive
categorization to the cross-platform tools, defines the pros and cons of each approach and compares the
cross-platform mobile development solutions.
This document provides an overview of the history and current state of mobile application development. It discusses the evolution of mobile operating systems from early Palm OS and Symbian to current leaders like Android and iOS. It also covers development frameworks including native, non-native like PhoneGap and Titanium, and the future of wearable technology.
The document discusses the history and current state of mobile application development. It begins with definitions and a brief history starting from the early 1990s. It then covers major platforms and operating systems that have emerged over time like Palm OS, Java ME, Symbian, Android, iOS, BlackBerry, and Windows Phone. Current development approaches including native frameworks and non-native alternatives like PhoneGap and Titanium are also summarized. The document concludes with a discussion of emerging areas like wearable technology and devices like Google Glass and Samsung Galaxy Gear.
Mobile Developer's Guide To The Galaxy, 14th EditionMarco Tabor
The latest edition of the community-driven handbook on mobile technologies. 256 pages packed with everything you need to know to start your mobile business: Which platforms exist and what's their potential? What about cross-platform app development? How do I create an app concept that works? How do I implement location-based services, NFC, mobile analytics, augmented reality or media content? What do I need to know about accessibility, monetization, security and app testing?
20 experts share their know-how in this book and you are invited to join them! See www.enough.de/mdgg for details.
Overview of Mobile Development PlatformsMike Wolfson
This document summarizes and compares several major mobile platforms including Apple iOS, Google Android, RIM Blackberry, Microsoft Windows Phone 7, Palm webOS, and Nokia Symbian. It discusses the developer tools, costs, and restrictions associated with each platform. It also notes trends in the mobile industry like continued fragmentation, expansion into new devices, and increasing patent litigation between companies.
Similar to Mobile Developers Guide To The Galaxy (20)
Sevenval Technologies is a frontend development company with 18 years of experience and over 170 employees across two locations in Cologne and Berlin. They provide a full range of services including UX design, digital strategy, development, hosting, and quality assurance. Their solution involves customizing the frontend and intelligently using existing backend systems for improved usability while maintaining flexibility. They aim to optimize speed, usability, and security for customers.
The document summarizes mobile device trends from Sevenval's monthly web traffic analysis for September 2015. It shows that the top 10 mobile devices are all Samsung phones, led by the Galaxy SII. It also shows that the top operating systems are Android and iOS, and that over 6,000 different devices access mobile websites globally each month, with the top 5 devices making up 38.9% of traffic but the long tail of other devices accounting for 61.1% of traffic. It concludes that for responsive web design, one must consider all possible combinations of unique client devices, browsers, and operating systems, of which there are over 100,000 in the current market.
The document analyzes mobile device trends from September 2015, including the top 10 mobile devices by web traffic, changes in traffic from August to September 2015, top mobile browsers and operating systems, statistics on iOS and Android versions, and the large number of unique client combinations from different devices, browsers and operating systems that websites must account for in design. It also briefly describes some products from Sevenval for responsive design, performance optimization and rapid development.
This document summarizes mobile device and browser trends based on data from Sevenval in August 2015. The top mobile devices were various iPhone and Samsung Galaxy models, with the iPhone 6 and 5 as the most popular. The top mobile browsers were Google Chrome for Android, Apple Mobile Safari, and Google Android Browser. Google Android accounted for 61% of mobile web traffic, followed by Apple iOS at 35%. The document also provides statistics on operating system and browser versions in use.
The document summarizes mobile device trend data from July 2015. It finds that the top mobile devices by traffic are various iPhone and Samsung Galaxy models, with the iPhone 6 and 5 being the highest. The most used mobile browsers are Google Chrome for Android and Apple Mobile Safari. The dominant operating systems are Android and iOS, making up over 95% of the market. It concludes that there are over 100,000 combinations of devices, browsers, and operating systems that must be accounted for in mobile web design.
This document summarizes mobile device and browser trends from a June 2015 report by Sevenval. The top three mobile devices were the iPhone 6, iPhone 5, and iPhone 4(S). The iPhone 6 saw significantly higher traffic than the Samsung Galaxy S6 since its 2014 release. Apple's Safari and Google's Android Chrome were the most used mobile browsers. The majority of mobile traffic was from Android and Apple operating systems. There were over 7,000 unique device models and nearly 100,000 combinations of devices, browsers and operating systems that web content needs to support.
Unsere Webtraffic-Zahlen für den Monat Mai 2015 sind veröffentlicht. Wie im Vormonat dominiert wieder das iPhone. Zuletzt konnte vor allem das iPhone 6 an Anteilen gewinnen.
Unter dem Motto: Safety First, Mobile First
fand am 1. Juni 2015 in Wien der 26. Mobile Monday.at statt.
Markus Dejmek (Country Manager Sevenval Österreich) sprach u.a. über
Mobilgeddon – warum die Versicherungsbranche die Mobilisierung beschleunigen muss
The document summarizes mobile device trends from Sevenval's April 2015 database. It finds that the top mobile devices by traffic are Samsung Galaxy phones, with Google Chrome the most used mobile browser. The dominant operating systems are Android at 61% and Apple at 35%. It also provides statistics on iOS and Android version usage and notes there are over 92,000 possible unique client combinations of device, browser and operating system that developers need to consider for responsive web design.
The document summarizes mobile device and browser trends from Sevenval's March 2015 database. It finds that the Samsung Galaxy S5, iPhone 6, and iPhone 5 were the top mobile devices by web traffic. Google Chrome and Apple Mobile Safari were the most used mobile browsers. The majority of mobile traffic came from Android and Apple operating systems. It also notes there are over 88,000 combinations of unique clients defined by device, browser, and operating system.
The document summarizes trends in mobile devices and browsers based on data from Sevenval's database in January 2015. It finds that the top mobile devices are various iPhone and Samsung Galaxy models, with the iPhone 5 and iPhone 6 being the most popular individually. The most used mobile browsers are Google Chrome for Android and Apple Mobile Safari. The majority of mobile traffic comes from Android and iOS operating systems. It also notes there are over 84,000 combinations of unique clients defined by device, browser, and operating system.
This document summarizes mobile device trends from Sevenval's January 2015 database. The top 10 mobile devices by web traffic are listed, with the iPhone 5 in first place at 29%. When comparing December 2014 to January 2015 traffic, iPhone models saw an increase while Samsung models decreased slightly. The most popular mobile browsers and operating systems are also shown, with Android at 62% and Google Chrome the top browser. The document notes there are over 6,956 different devices accessing mobile websites.
The document discusses trends in mobile devices and browsers based on data from Sevenval's database from January 2015. It shows that the top mobile devices by traffic are various Samsung Galaxy and iPhone models, with the iPhone 5 and iPhone 4(S) being the top two. The most popular mobile browsers are Google Chrome for Android and Apple Mobile Safari. The majority of mobile traffic comes from Android and Apple operating systems. It also discusses trends in iOS and Android version adoption and notes there are over 81,000 combinations of unique clients based on device, browser and operating system.
The document discusses mobile device trends based on data from Sevenval's database in November 2014. It finds that Samsung devices like the Galaxy SIII and SIV accounted for 36% of mobile web traffic, while Apple devices accounted for 36%. The top mobile operating systems were Android at 61% and iOS at 35%. It also notes that there are over 6,800 different devices accessing mobile websites worldwide and that mobile fragmentation is significant.
This document summarizes mobile device and operating system trends from September 2014. The iPhone 5 and various Android smartphones generated the most mobile web traffic. The iPhone accounted for a larger percentage of traffic than Samsung devices. Most mobile websites were accessed using the Android operating system and Apple's iOS. There are thousands of unique device, browser, and operating system combinations demonstrating the high level of mobile fragmentation.
This document summarizes mobile device and operating system trends based on data from Sevenval's database in July 2014. It finds that the top mobile devices by web traffic are various iPhone and Samsung Galaxy models. The top operating systems are Android, iOS, and Blackberry. The most used browsers on mobile are Android's built-in browser, Apple Mobile Safari, and Google Chrome for Android. Charts also show the distribution of iOS and Android operating system versions over time. The document concludes that mobile fragmentation is significant with over 60,000 unique client combinations of device, browser, and operating system.
The document summarizes device trends from a May 2014 report by Sevenval. It found that while only 7 devices dominated 52% of the mobile market, there was significant fragmentation with over 4,770 unique devices accessing mobile websites. The top 20 devices accounted for 52% of traffic, but the long tail of other devices made up the remaining 48%. It concludes that mobile fragmentation is significant and will continue due to the wide range of operating systems, browsers, and devices in the market.
The document summarizes mobile device trends from a January 2014 report by Sevenval. It finds that over 5,220 different mobile devices access the mobile web worldwide, with the top 5 devices dominating 50.03% of the market and a long tail of other devices making up the remaining 49.97%. It also notes the wide variety of operating system versions in use due to differences in how iOS and Android devices receive updates.
7 Most Powerful Solar Storms in the History of Earth.pdfEnterprise Wired
Solar Storms (Geo Magnetic Storms) are the motion of accelerated charged particles in the solar environment with high velocities due to the coronal mass ejection (CME).
TrustArc Webinar - 2024 Data Privacy Trends: A Mid-Year Check-InTrustArc
Six months into 2024, and it is clear the privacy ecosystem takes no days off!! Regulators continue to implement and enforce new regulations, businesses strive to meet requirements, and technology advances like AI have privacy professionals scratching their heads about managing risk.
What can we learn about the first six months of data privacy trends and events in 2024? How should this inform your privacy program management for the rest of the year?
Join TrustArc, Goodwin, and Snyk privacy experts as they discuss the changes we’ve seen in the first half of 2024 and gain insight into the concrete, actionable steps you can take to up-level your privacy program in the second half of the year.
This webinar will review:
- Key changes to privacy regulations in 2024
- Key themes in privacy and data governance in 2024
- How to maximize your privacy program in the second half of 2024
Best Practices for Effectively Running dbt in Airflow.pdfTatiana Al-Chueyr
As a popular open-source library for analytics engineering, dbt is often used in combination with Airflow. Orchestrating and executing dbt models as DAGs ensures an additional layer of control over tasks, observability, and provides a reliable, scalable environment to run dbt models.
This webinar will cover a step-by-step guide to Cosmos, an open source package from Astronomer that helps you easily run your dbt Core projects as Airflow DAGs and Task Groups, all with just a few lines of code. We’ll walk through:
- Standard ways of running dbt (and when to utilize other methods)
- How Cosmos can be used to run and visualize your dbt projects in Airflow
- Common challenges and how to address them, including performance, dependency conflicts, and more
- How running dbt projects in Airflow helps with cost optimization
Webinar given on 9 July 2024
An invited talk given by Mark Billinghurst on Research Directions for Cross Reality Interfaces. This was given on July 2nd 2024 as part of the 2024 Summer School on Cross Reality in Hagenberg, Austria (July 1st - 7th)
Blockchain technology is transforming industries and reshaping the way we conduct business, manage data, and secure transactions. Whether you're new to blockchain or looking to deepen your knowledge, our guidebook, "Blockchain for Dummies", is your ultimate resource.
Mitigating the Impact of State Management in Cloud Stream Processing SystemsScyllaDB
Stream processing is a crucial component of modern data infrastructure, but constructing an efficient and scalable stream processing system can be challenging. Decoupling compute and storage architecture has emerged as an effective solution to these challenges, but it can introduce high latency issues, especially when dealing with complex continuous queries that necessitate managing extra-large internal states.
In this talk, we focus on addressing the high latency issues associated with S3 storage in stream processing systems that employ a decoupled compute and storage architecture. We delve into the root causes of latency in this context and explore various techniques to minimize the impact of S3 latency on stream processing performance. Our proposed approach is to implement a tiered storage mechanism that leverages a blend of high-performance and low-cost storage tiers to reduce data movement between the compute and storage layers while maintaining efficient processing.
Throughout the talk, we will present experimental results that demonstrate the effectiveness of our approach in mitigating the impact of S3 latency on stream processing. By the end of the talk, attendees will have gained insights into how to optimize their stream processing systems for reduced latency and improved cost-efficiency.
Advanced Techniques for Cyber Security Analysis and Anomaly DetectionBert Blevins
Cybersecurity is a major concern in today's connected digital world. Threats to organizations are constantly evolving and have the potential to compromise sensitive information, disrupt operations, and lead to significant financial losses. Traditional cybersecurity techniques often fall short against modern attackers. Therefore, advanced techniques for cyber security analysis and anomaly detection are essential for protecting digital assets. This blog explores these cutting-edge methods, providing a comprehensive overview of their application and importance.
Are you interested in dipping your toes in the cloud native observability waters, but as an engineer you are not sure where to get started with tracing problems through your microservices and application landscapes on Kubernetes? Then this is the session for you, where we take you on your first steps in an active open-source project that offers a buffet of languages, challenges, and opportunities for getting started with telemetry data.
The project is called openTelemetry, but before diving into the specifics, we’ll start with de-mystifying key concepts and terms such as observability, telemetry, instrumentation, cardinality, percentile to lay a foundation. After understanding the nuts and bolts of observability and distributed traces, we’ll explore the openTelemetry community; its Special Interest Groups (SIGs), repositories, and how to become not only an end-user, but possibly a contributor.We will wrap up with an overview of the components in this project, such as the Collector, the OpenTelemetry protocol (OTLP), its APIs, and its SDKs.
Attendees will leave with an understanding of key observability concepts, become grounded in distributed tracing terminology, be aware of the components of openTelemetry, and know how to take their first steps to an open-source contribution!
Key Takeaways: Open source, vendor neutral instrumentation is an exciting new reality as the industry standardizes on openTelemetry for observability. OpenTelemetry is on a mission to enable effective observability by making high-quality, portable telemetry ubiquitous. The world of observability and monitoring today has a steep learning curve and in order to achieve ubiquity, the project would benefit from growing our contributor community.
Choose our Linux Web Hosting for a seamless and successful online presencerajancomputerfbd
Our Linux Web Hosting plans offer unbeatable performance, security, and scalability, ensuring your website runs smoothly and efficiently.
Visit- https://onliveserver.com/linux-web-hosting/
Understanding Insider Security Threats: Types, Examples, Effects, and Mitigat...Bert Blevins
Today’s digitally connected world presents a wide range of security challenges for enterprises. Insider security threats are particularly noteworthy because they have the potential to cause significant harm. Unlike external threats, insider risks originate from within the company, making them more subtle and challenging to identify. This blog aims to provide a comprehensive understanding of insider security threats, including their types, examples, effects, and mitigation techniques.
BT & Neo4j: Knowledge Graphs for Critical Enterprise Systems.pptx.pdfNeo4j
Presented at Gartner Data & Analytics, London Maty 2024. BT Group has used the Neo4j Graph Database to enable impressive digital transformation programs over the last 6 years. By re-imagining their operational support systems to adopt self-serve and data lead principles they have substantially reduced the number of applications and complexity of their operations. The result has been a substantial reduction in risk and costs while improving time to value, innovation, and process automation. Join this session to hear their story, the lessons they learned along the way and how their future innovation plans include the exploration of uses of EKG + Generative AI.
YOUR RELIABLE WEB DESIGN & DEVELOPMENT TEAM — FOR LASTING SUCCESS
WPRiders is a web development company specialized in WordPress and WooCommerce websites and plugins for customers around the world. The company is headquartered in Bucharest, Romania, but our team members are located all over the world. Our customers are primarily from the US and Western Europe, but we have clients from Australia, Canada and other areas as well.
Some facts about WPRiders and why we are one of the best firms around:
More than 700 five-star reviews! You can check them here.
1500 WordPress projects delivered.
We respond 80% faster than other firms! Data provided by Freshdesk.
We’ve been in business since 2015.
We are located in 7 countries and have 22 team members.
With so many projects delivered, our team knows what works and what doesn’t when it comes to WordPress and WooCommerce.
Our team members are:
- highly experienced developers (employees & contractors with 5 -10+ years of experience),
- great designers with an eye for UX/UI with 10+ years of experience
- project managers with development background who speak both tech and non-tech
- QA specialists
- Conversion Rate Optimisation - CRO experts
They are all working together to provide you with the best possible service. We are passionate about WordPress, and we love creating custom solutions that help our clients achieve their goals.
At WPRiders, we are committed to building long-term relationships with our clients. We believe in accountability, in doing the right thing, as well as in transparency and open communication. You can read more about WPRiders on the About us page.
Transcript: Details of description part II: Describing images in practice - T...BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and slides: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
3. Developer’s Guide
Table of Contents
5 About the Authors
7 Introduction
8 Application Environments Overview
8 Native Applications
10 J2ME / Java ME
10 Flash Lite
10 BREW
12 Widgets
13 Websites
13 SMS Text Messaging
14 Programming J2ME / Java ME Apps
15 Prerequisites for Mobile Java Development
16 Implement your App
17 Testing
18 Cover‘em All: Porting
21 A Question of Trust: Certification
22 Distributing your J2ME Application
23 Bringing Your Mobile Content to the Mobile Web:
“Keep it small, keep it simple”
23 Why a mobile web page
25 Some history on the mobile web
26 How to adapt content for the mobile user
28 Satisfy the interpreter of your content: The browser
30 Let’s do some pigeonholing: Device categories
3
4. 34 Learn more — on the web
35 Now what — which Enviroment Should I Use?
38 Epilogue
This Developer Guide is licensed under the Creative Commons
Some Rights Reserved License.
4
5. Developer’s Guide
About the Authors
Robert Virkus / Enough Software
Robert works in the mobile space since 1998. He experienced the Java
fragmentation first hand by developing and porting a mobile sports
betting client on the Siemens SL42i phone, which happened to be the
first mass market phone with an embedded Java Virtual Machine. With
this experience he launched the Open Source J2ME Polish project in
2004 that aims to overcome the device fragmentation barrier. He is
the founder and CEO of Enough Software, the company behind J2ME
Polish.
www.enough.de www.j2mepolish.org
Roland Gülle / Sevenval
Roland joined the mobile industry in 2001. At Sevenval he is respon-
sible for the development of the adaptation technology and the FITML
Platform which allows developers to create mobile internet portals.
Roland is an active member of the the Mobile Web Initiative (MWI) and
several open source projects.
www.7val.com
Thibaut Rouffineau / WIP
Community and passion builder with a mobile edge, Thibaut has been
conversing with the mobile developer community for the past 4 years as
the head of developer engagement at Symbian, where he spearheaded
the migration to open source. Today he is the VP for Developer Partner-
ships at WIP (Wireless Industry Partnership).
www.wipconnector.com
5
7. Developer’s Guide
Introduction
This guide is aimed at developers who (want to) realize their ideas
on mobile handsets. We try to outline typical problems and how to
overcome them.
Developing for mobile handsets is a schizophrenic experience – on one
side there is the never-ending stream of innovations and new tech-
nologies, on the other side it can take a painfully long time until new
technologies are actually used by the end customers.
The most important issues for mobile application developers are for
sure fragmentation and distribution. Thankfully solutions for those
problems do exist.
Development is a passion – have fun in
the mobile world!
7
8. Developer’s Guide
Application Environments
You can choose between different environments for realizing your mo-
bile vision. This section describes the most common environments and
outlines differences between them. A more detailed description follows
in the environment specific chapters later onwards.
Native Applications
You can also create native applications for many mobile handsets.
There are a lot of mobile operating systems used in the market today
– some are Open Source, some are not. Most important OS are (al-
phabetically) Android, BlackBerry, Maemo, Moblin, OS X, Symbian and
Windows Mobile. All these OS allow you to creative native applications
for them without establishing a business relationship with the respec-
tive vendor. Most mass market phones are, however, equipped with em-
bedded operating systems that cannot be programmed for by outsiders.
Examples include but are not limited to Nokia Series 40, Samsung SGH
and Sony Ericsson Java Platform phones.
Main benefits for programming native applications include the best
possible integration of your application and often a very good perfor-
mance. Typical drawbacks are the required effort and the complexity of
supporting several native platforms (or the limitation of your app to
only one platform). Also most mass market handsets cannot be pro-
grammed natively.
8
9. The following table provides an overview about the main mobile
operating systems:
OS Language(s) Remarks
Android Java Open Source OS (based on Linux)
developer.android.com
Blackberry Java Is also J2ME compatible, but the
native APIs provide better integration.
http://na.blackberry.com/eng/developers
LiMO C, C++ Open Source OS (based on Linux)
www.limofoundation.org
Maemo C, C++ Open Source OS (based on Linux)
http://maemo.org/development
Moblin C, C++ Open Source OS (based on Linux)
moblin.org
OS X / iPhone Objective-C, C Requires Apple Developer Account
http://developer.apple.com/iphone
Symbian C, C++, others Open Source OS
Some Series 60 compatible phones
support further languages like Python.
Most Symbian phones support J2ME.
www.symbian.org
Web OS HTML, CSS, Widget style programming, OS is
JavaScript based on Linux
http://developer.palm.com
Windows C#, C You can choose between the .NET
Mobile Compact Framework and programming
Windows Mobile directly. Most Windows
Mobile phones also come with a J2ME
compatible JVM preinstalled.
developer.windowsmobile.com
9
10. J2ME / Java ME
Around 80% of all mobile handsets shipped in 2008 support the mo-
bile Java standard (J2ME/Java ME), so Java is by far the most widely
distributed application environment. In contrast to many other en-
vironments, J2ME is a standard rather than a product, which can be
implemented by anyone (who pays Sun the corresponding license fees
that is). Standardization is the strength of J2ME but at the same time
it is the source for many fragmentation problems.
On many handsets with embedded operating systems, J2ME is the only
way to realize client side applications. The main problem is the frag-
mentation, meaning the little differences between the implementations
and handsets.
Flash Lite
Flash Lite is the mobile edition of Flash, which pretty much is the same
as an older version of Adobe’s web Flash product. Flash Lite gains trac-
tion and is especially favored by many designers, since they know the
tools already.
Flash Lite features a powerful UI but it lacks a good integration into
the native devices, although this is improving. Programming Flash
Lite is relatively easy thanks to its Action Script language that is
very similar to Java Script. The drawback is its poor performance and
small market share in comparison to J2ME.
BREW
The Binary Runtime Environment for Wireless (BREW) is a low level
programming environment pushed forward by Qualcomm. Nowadays it
is under immense pressure since there is only one operator in the US
left (Sprint) and has not been adopted widely anywhere else (some in
10
11. India, some in Korea). On the positive side there are still around some
50 million US customers using BREW handsets. BREW is programmed
with a low level C based API.
11
12. Widgets
There are several widget environments that you can choose from. Main
benefit of these environments are the simple programming, main draw-
back is that you need to ensure that your customers will install both
– the widget player as well as your widget. More and more devices
feature, however, a preinstalled widget player – not necessary for the
environment that you have chosen, though.
The other siginificant drawback is that widgets do only allow a very
low-level access to the handsets functionalities.
All these environments use XML, a script language (e.g. JavaScript)
and a page description language (like HTML) for realizing a widget.
The following table gives you an overview about popular widget frame-
works:
Environment Language(s) Remarks
Nokia Web XML, http://www.forum.nokia.com
Runtime HTML, CSS,
Widgets JavaScript
Starmobi XML, CSS, The Starmobi JavaScript API allows
JavaScript you to script apps similar to J2ME,
German only.
www.starmobi.de/index.php?id=developer
W3C / XML, Vodafone, China Mobile and other
Vodafone HTML, CSS, companies try to push the W3C widget
Widgets JavaScript standard for mobile adoption.
http://widget.vodafone.com/dev
Samsung XML, innovator.samsungmobile.com
HTML, CSS,
JavaScript
12
13. Websites
Webpages are supported by all phones, so in principle this should be
the environment of choice to get the widest possible reach (after SMS
texting). The only problem is the sheer number of browsers and they
varying feature sets. Some browsers are very powerful and support CSS
as well as JavaScript, others are less sophisticated XHTML only. Thank-
fully the old WAP standard with its WML pages does not play any sig-
nificant role nowadays.
Main problems for web pages are that they are only available online and
that they cannot access device features today. Main benefits are the
easy development and a deployment that lies solely in your hands.
SMS Text Messaging
Almost everybody who has a mobile phone is also texting. Texting pro-
vides the limitation that any interaction needs to be pressed into 160
characters and that it can be quite costly to send out text messages in
bulk. On the positive side it enjoys a global audience of any age.
13
14. Developer’s Guide
Programming J2ME / Java ME
Apps
Programming J2ME apps is a fun and rewarding experience. The capa-
bilities of the Java platform are constantly evolving thanks to the Java
Community Process (www.jcp.org) that standardizes new APIs (like the
Wireless Messaging API) and even whole platforms (like the Mobile
Service Architecture).
For realizing your idea in Java you need to follow these steps:
1. Prerequisites
2. Implement
3. Test
4. Port
5. Certify
6. Distribute
These steps are detailed in the following sections.
14
15. Prerequisites for Mobile Java
Development
A mobile Java application (MIDlet) is compiled, obfuscated, preveri-
fied and packaged. To implement your application you need a couple
of things:
— the Java SDK1) (not the Java Runtime Environment) and IDE of
your choice, e.g. Eclipse 2) possibly with Mobile Tools for Java
(MTJ), NetBeans3) with its mobility pack, or IntelliJ.4)
— an Emulator, e.g. the Wireless Toolkit5), the Micro Emulator 6)
or a vendor specific emulator.
— Depending on your setup you may also need an obfuscator like
ProGuard7). If you build applications professionally you will
probably also want to use a build tool like Maven8) or Ant.9)
— You may want to check out J2ME Polish, the Open Source frame
work, for building your application for various devices.10)
A complete installation and setup guide is out of scope of this guide,
please refer to the respective documentation of these tools. Beginners
often like NetBeans with an installed mobility pack.
Also download and read the JavaDocs for the most important technolo-
gies and APIs.
You can download most JavaDocs from www.jcp.org but there are a
couple of useful vendor specific APIs that needed to be tracked down
manually from the vendor’s pages (Nokia UI-API or Samsung APIs, for
example).
1) java.sun.com 6) www.microemu.org
2) www.eclipse.org 7) proguard.sf.net
3) www.netbeans.org 8) maven.apache.org
4) www.jetbrains.com 9) ant.apache.org
5) java.sun.com/products/sjwtoolkit 10) www.j2mepolish.org
15
16. Implement Your App
The J2ME environment is pretty much straight forward, the basis is
formed by the Connected Limited Device Configuration (CLDC) and the
Mobile Internet Device Profile (MIDP), which are both quite easy to un-
derstand. Similar to the good ol’ fashioned Applets you extend javax.
microediton.midlet.MIDlet in your main class and then you are ready
to go.
You can create the UI of your app in different ways:
— Highlevel LCDUI components: use the components found in
the javax.microedition.lcdui package, e.g. Form or List.
— Lowlevel LCDUI: use javax.microedition.lcdui.Canvas for
controlling every pixel of your UI.
— SVG: Scalable vector graphics defined in JSR 287
jcp.org/en/jsr/detail?id=287.
There are also different products out there to help you with the UI
development:
— J2ME Polish: compatible with the highlevel LCDUI framework,
separates the design in CSS, you can also use HTML for the user
interface (www.j2mepolish.org).
— LWUIT: a Swing inspired UI framework
(lwuit.dev.java.net).
— Mewt: Use XML for defining the UI (mewt.sourceforge.net).
— TWUIK: A powerful “Rich Media Engine”
(www.tricastmedia.com/twuik)
There is a rich open source scene in the J2ME sector. Interesting projects
can be found via blog on opensource.ngphone.com. You will also find
many interesting projects on Sun’s page1), for example the Bluetooth
project Marge2).
1)mobileandembedded.dev.java.net
2)marge.dev.java.net
16
17. Testing
Thanks to the fragmentation, testing your applications is absolutely
vital. Test as early and as often as you can on real devices. Testing on
emulators cannot substitute testing on real devices – you cannot com-
pare your machine with 3GHz Dual CPU, 4 GB of RAM and broadband
internet connection with typical mobile phones. Some emulators are
quite good (my personal favorites are BlackBerry and Symbian), but
there are some things you have to test in real:
— UI: the experience of the user interface can differ in real
sunlight when you’re out and about. It’s a mobile device –
most users will be on the move!
— Location: if you use location information within your app:
move – both fast and slowly.
— Multimedia: support for audio, video playback and recording
facilities can differ dramatically between devices and their
respective emulators.
— Internet connectivity: establishing internet connections
can take an incredible amount of time. Connection delay and
bandwidth depend on the network, its current strength and
the number of simultaneous users.
Thankfully some vendors provide subsidized or even free remote
access to selected devices:
— Nokia: apu.ndhub.net
— Sony Ericsson: developer.sonyericsson.com/site/global/
techsupport/virtuallab/p_virtual_lab.jsp
— Samsung: innovator.samsungmobile.com/bbs/lab/view.
do?platformId=2
17
18. If you require to test network connectivity on a number of carriers or
if you need to access certain devices of a specific carrier, you can use
Device Anywhere1) for your testing needs.
Mob4hire2) provides crowdsourcing services. Of course there are vari-
ous testing companies as well, that provide testing and QA services,
e.g. Absolute Quality3) or Mobiquest4).
Unit testing can be done with MoMEUnit5) or CLDC Unit6), coverage
testing with Cobertura for J2ME7).
Cover‘em All: Porting
One of the strengths of the mobile Java environment is that this is
standard, so it can be implemented by various vendors that compete
with each other. The bad news is that a standard has to be interpreted,
and interpretation causes differences. Different implementations also
suffer from different bugs, which makes things not really easier. In the
next sections we outline different strategies for porting your J2ME ap-
plications to both all J2ME handsets and to different platforms.
Direct Support
The best but the hardest solution is to code directly for different
device groups and platforms. This means to create a J2ME app for
MIDP devices, a native BlackBerry app, a native Windows Mobile
app, a Symbian app, an iPhone app, a Web OS app, and so and so on.
As you can imagine, this approach has the potential to bring the very
best user experience, since you can really adapt your application to
each platform. At the same time your development costs will skyrock.
We advise to use another strategy first until your idea has been proven
to be a success.
1) www.deviceanywhere.com 5) momeunit.sourceforge.net
2) www.mob4hire.com 6) snapshot.pyx4me.com/pyx4me-cldcunit
3) www.absolutequality.com 7) www.cobertura4j2me.org
4) www.mobiquest.net
18
19. Least Common Denominator
You can prevent many porting issues by limiting the functionalities
of your application to the least common denominator. In the J2ME
world this means CLDC 1.0 and MIDP 1.0. Depending on the target
region for the application you might also consider to use either the
extensions Java Technology for the Wireless Industry (JTWI, JSR 185)
or the Mobile Service Architecture (MSA, JSR 205). Both extensions
are supported by many modern devices and provide a lot more power,
though in some regions like Africa, South America or India you should
be aware that you are limiting the number of your potential users by
taking this step.
Using the least common denominator typically is easier, as there is less
functionalities to care about. However, the user experience may suffer
when limiting your application in this way. Also this approach won’t
help you to port your app to different platforms like Android or the
iPhone. In short: use the least common denominator for simple appli-
cations, but be careful to use this approach for complex applications.
Player Based Solutions
There are various player solutions on the market which mostly provide a
consistent set of APIs across various platforms. The player itself has been
ported to different platforms and it interprets or executes the applica-
tion code. Cool player solutions include PhoneGap1) and Gear.2)
Player technologies provide an easy and compelling way to realize so-
lutions across a variety of platforms. One drawback can be that player
concepts often need to use the least common denominator for realizing
a consistent API across platforms, it can be difficult or not possible at
all to use platform or device specific functionalities in your applica-
tion.
1) www.phonegap.com
2) www.digitalapes.net/en/applications/gear
19
20. Porting Frameworks
Porting frameworks automatically adapt your application to different
devices and platforms. Such frameworks typically feature following in-
gredients:
— Client library that simplifies development
— Build tools chain that converts code and resources to
application bundles
— Device database that provides information about devices
— Cross compilers to port your application to different
platforms
In the J2ME world there are various frameworks to choose from: Xpress
Suite from JavaGround1) provides porting against revenue sharing. Cel-
sius from Mobile Distillery2) is licensed per month. Bedrock from Me-
tismo3) provides a suite of cross compilers on a yearly license fee. J2ME
Polish from Enough Software4) is available under both the GPL Open
Source license and commercial ones. Going the other direction (from
C++ to Java ME) is also possible with the MoSync Open Source solution
from Mobile Sorcery5). Good porting frameworks allow you to use plat-
form and device specific code in your project, so that you can provide
the best user experience. In other words: A good framework does not
hide device fragmentation, but makes the fragmentation manageable.
1) javaground.com 4) www.j2mepolish.org
2) www.mobile-distillery.com 5) www.mosync.com
3) metismo.com
20
21. A Question of Trust: Certification
The mobile Java standard differentiates between signed and unsigned
applications. Some handset functionalities are only available to trusted
applications. Which features are affected and what happens if the ap-
plication is not signed but uses one of those features largely depends
on the implementation. On one phone the user might be asked once
to allow this functionality, on another he’ll be asked every time the
feature is being used and on the third one you won’t be able to use the
feature at all without signing.
Most implementations also differentiate between the certification
authorities who have signed an application:
Applications signed by the manufacturer of a device enjoy the highest
security level and can access every handset they desire. Applications
signed with a carrier certificate are on a similar level.
Applications signed by JavaVerified1), Verisign2) or Thawte3) are on the
lowest security level. The mad thing is that not every phone carries all
necessary root certificates. And some well known vendors even strip
away all root certificates. The result is quite a mess, so consider sign-
ing your application only when required, e.g. when deploying to an
app store or when you absolutely need access to security constrained
features.
1) javaverified.com 3) www.thawte.com/code-signing
2) www.verisign.com/code-signing
21
22. Distributing Your J2ME Application
Unlike the iPhone, you can install J2ME applications directly on your
phone – either over bluetooth or over the air (OTA) using a webserver.
Thanks to the universal app stores, nowadays distribution is easier
than ever. They manage the payment, hosting and advertisements and
receive a revenue share for that.
— Ovi1) targets Nokia users worldwide and provides a 70% revenue
share for the developer (of Gross sales, net of refunds and
returns, less applicable taxes and, where applicable, fixed
operator billing costs).
— Java Store2) plans to sell Java based content
— The Samsung App Store3) distributes application for Samsung
handsets
— LG also distributes apps on http://www.lgapplication.com
— Handmark provides a carrier and vendor independent mobile
store.4)
— Carriers also get into the game, e.g. Sprint5) or O2.6) Basically
almost everyone has announced an app store.
— GetJar is one of the oldest distributors for free mobile
applications.7)
There are various vendors who provide solutions for provisioning of
Java applications over Blueooth, including Waymedia8), Futurlink9) and
Broadburst.10)
1) publish.ovi.com 6) www.o2litmus.com
2) store.java.com 7) www.getjar.com
3) applications.samsungmobile.com 8) www.waymedia.it
4) www.handmark.com 9) www.futurlink.com
5) softwarestore.sprint.com 10) www.broadburst.com
22
23. Developer’s Guide
Bringing Your Content to the
Mobile Web: »Keep it simple,
keep it small«
Why a mobile web page?
When discussing the mobile internet, the first question is: Why shall I
setup a special website for mobile devices?
On one hand there are automatic adaptation engines (like Google or
Opera Mini), which automatically generate mobile versions of any web-
site. On the other hand, the mobile browsers are getting more powerful
and capable of displaying any website (e.g. iPhone)
Both approaches are solving the problem technically but ignore the
primal difference:
The usage context and its meaning for the content
The usage pattern at a desktop computer is often described as „Hunt &
Gather“. The mobile usage is totally different. When using internet on
the mobile handset, the user is usually on the move. He wants to know
more about his surrounding or just fill some minutes. Therefore, mobile
internet usage is often described as „Quick Enjoyment“.
Applications have to take these differences into account. For example,
a search mask for stationary users has to offer comprehensive options,
on the mobile handset it has to be more straight-forward, focused on
the certain action.
These adjustment cannot be realized by a machine. This is one reason
why it is indispensable to create special mobile versions of web-
sites.
23
24. But the user’s requirements regarding the content are not the only
aspect that has to be taken into account, mobile developers also have
to think about:
The usability on mobile hardware
The mobile user has no mouse, often he has no real keyboard and the
size of the screen is very limited. This means, the content of a mobile
website has to be arranged accordingly: Images should not be too
large, all relevant elements should be easily accesible although the
user is not able to move a cursor freely along the site.
The best is to test the usability of a site under real-life circumstances:
Take your mobile handset to a busy public place and try to find all
relevant info of your application by just using one hand. You will see
very quickly where your mobile site shall still be trimmed.
But apart from things like markup, image formats and navigation, you
should never forget about the most valuable good of the mobile user:
Battery power. Complex websites with a lot of JavaScript, CSS and
Flash elements need a lot of processing power which means battery
power.
24
25. Some History on the Mobile Web
WAP: The stone age of mobile internet
In the beginning, everybody in the business expected the mobile
internet to be a cashcow. The WAP technology made it possible to
send small texts on monochrome displays and b/w images in the WBMP
format to the user’s cellphones, the industry charged him for that by
inventing complicated data transfer rates or strange subscription mod-
els. Many players expected to get rich by selling information which was
already available for free on the internet.
The Wireless Markup Language WML which was used by that time was
another reason why the expected breakthrough did not happen as fast
as some were thinking: While the different internet browsers (Internet
Explorer and Netscape) allowed a „dirty“ html, WML requested a valid
XML structure and proper UTF-8 encoding. The usage of images was
limited to black and white pictures which were a lot less sexy than
what the users knew from their home computers.
The first tries to lift the mobile internet to the next level were
made by NTT DoCoMo by inventing CHTML and Microsofts Windows
CE which worked best with HTML/3.2. But both of them were
just interludes which were replaced by XHTML/MP 1.0.
25
26. Current Situation
Today, 99% of all mobile browsers are still supporting XHTML/MP 1.0,
for many low-end devices this language still delivers the best results.
On the other hand, the so-called Full Web Browsers have to support
HTML/4.0, but they still have their differences when it comes to con-
tent-type or doctype and chose different views for distinguishing be-
tween mobile and desktop websites.
How to adapt content for the mobile
user
Static Version
Of course you can simply ignore the possibilities of automatic optimi-
zation and leave it up to the user: Create different versions of your
content, let the user start with the most low-level version and let him
decide manually which variation is the most comfortable one for his
device and usage patterns in a next step.
But since you are dealing with a user who is on the move and does not
want to spend a lot of time with finding out how to see properly what
you are delivering, this is probably not the best way to go…
Automatic adaptation technologies
To adapt the content to different devices, you basically need two com-
ponents: One logic that detects the device, knows about its browser
and its characteristics — a device database. The second component
interpretes these characteristics and adjusts the content accordingly.
The most popular Open Source device database is the WURFL project
(http://wurfl.sf.net) which offers comprehensive information via XML.
A lot of tools deliver APIs for detecting the browser, delivering its
properties and adjusting the content, the markup and the images. One
example for an Open Source project which adjusts content is MyMo-
bileWeb (http://mymobileweb.morfeo-project.org), financed by public
funds and Telefonica.
26
27. But of course there are also purely commercial providers. Again, some
are concentrating on device data and detection, others are focusing on
offering software platforms which adjust the content accordingly.
Examples for commercial device data and device detection
providers:
— dotMobi1) offers several APIs to access their device database
DeviceAtlas2) and intelligent detection
— DetectRight3)
Some commercial content adaptation software providers:
— Sevenval4), a platform independent technology which works via
HTTP and markup. This solution is available as a Service or can
be installed on Linux systems.
— Volantis Mobility Server5) is running on a variety of Java-based
web application servers and SQL-compliant databases. There are
two versions available: one Open Source Community version and
one professional version.
— Mobile Interaction Server6) is running on BEA, IBM WebSphere,
JBoss, Tomcat and Caucho Resin.
1) mtld.mobi 4) www.sevenval.com
2) deviceatlas.com 5) www.volantis.com
3) www.detectright.com 6) www.mobileaware.com
27
28. Satisfy the Interpreter of Your Content:
The Browser
Markup
Of course it would be great if there would be one universal markup
standard — unfortunately this is not the case. There are many stan-
dards, so be sure of validating your markup. The W3C offers an univer-
sal validator on http://validator.w3.org. Furthermore it is always good
to stick to UTF-8 encoding.
Of course the easiest way is creating a XHTML MP/1.0 site with
WCSS/1.0 and without JavaScript.
Page Width
Always use dynamic layout. Avoid static width settings in pixels, better
use percentage values. Even when using device databases, the brows-
ers still have different display methods (fullscreen, landscape, por-
trait) and only some allow displaying a scrollbar.
The web is dynamic, so is the hardware landscape — keep your layout
dynamic as well!
Images
Not everybody has a mobile data flatrate, so do not use images too
excessively, avoid any unnecessary images. To reduce data and proces-
sor workload, the images should always be scaled on the server and not
by the browser. ImageMagick offers the possibility to easily scale your
images: http://www.imagemagick.org
When thinking about the image format, GIF and JPEG are still the most
solid choice. Of course PNG offers more flexibility, but when it comes
to transparency, you cannot always be sure to what degree it is sup-
ported. And some operators still use image proxies which might not be
able to handle this.
28
29. Tables
For stationary web, tables are no longer used for webdesign. In the
mobile environment they are still an effective way to create simple
layouts — just avoid unnecessary nested tables and colspan / row-
span.
Even though it breaks the rules for valid XHTML MP/1.0, some brows-
ers need the attributes cellpadding=“0“ and cellspacing=“0“ for not
displaying unmeant spaces. CSS is simply not capable to assure this
with all browsers.
CSS
Do not use CSS excessively. CSS interpretation is sometimes not
properly implemented and shortens battery life. If you stick to the
WCSS/1.0 set, you are on the safe side.
When determining sizes, avoid to define them in pixels, use percent-
age values.
Fonts
Do not deal too arbitrarily with fonts: all browsers just dispose of a
limited set of font-types. Better focus on the font size. Use relative
values (small/medium/large) rather than fixed values (pixels) — the
browser knows best how many pixels to use for displaying a large, a
medium or a small font.
Cookies
You can of course use cookies and should do so, but only when really
needed. And never trust too much in them: although it might work
fine during one session, the cookie might get lost afterwards. This is
why you should always offer alternatives like an URL based param-
eter or a personalised bookmark for permanent settings.
29
30. Script / AJAX
According to www.device-trends.com, 93% of the mobile web users
who visited the associated websites, were using a browser which sup-
ports JavaScript, 70% were able to handle AJAX. So it would be wrong
not to use the possibilities of these technologies. But you should make
sure that your side works fine without them as well.
Let’s do some pigeonholing:
Device categories
You have no idea what kind of devices your visitors mostly use? Then
you should start low-level and implement a tool which detects the
devices who are accessing your site.
Several providers are offering this kind of analysis software:
— Sevenval www.device-trends.com
— TigTags www.tigtags.com/mobile_analytics/mobile_site_tracking
— AdMob www.admob.com
— Bango www.bango.com
Very roughly, mobile devices can be split into three categories with
very different requirements:
Simple Devices
Probably the vast majority of your users will access your site with a
basic handset like described by the W3C in the Default Delivery Con-
text1) or by Luca Passani in his baseline device description.2)
1) www.w3.org/TR/mobile-bp/#ddc
2) www.passani.it/gap/#baseline
30
31. To fit their needs, these are our recommendations:
— XHTML MP/1.0
— screensize: 176x144
— GIF or JPEG image format
— max. 20kb page size (incl. images, CSS)
— basic Table Support, without „rowspan“,“colspan“ - no nested
tables
— minimal CSS (WCSS 1.0)
Of course even these basic characteristics exceed the possibilities of
many older handsets, but people who tend to use the mobile internet
usually own handsets who should properly display pages that follow
the guidelines above. Surfing the internet with much older devices is
no fun anyway.
Full Web Browser-supported Devices
Full Web Browsers are characterized by their capability to display any
website. These are all webkit based browsers, Opera Mobile, Microsoft
Internet Explorer, Netfront (version 3.4 and later), UCWEB or Fennec.
Devices who use a Full Web Browser do not necessarily require any
technological concessions regarding website design, but we suggest to
follow these guidelines:
— HTML/4.0 Strict
— screensize: 240x320
— GIF or JPEG Images, PNG without alpha transparency
— max. 50kb page size (incl. images, CSS)
— basic table support, without „rowspan“,“colspan“ - no nested
tables
— keep CSS simple, tables are not bad
— script is allowed, but not needed (avoid unneeded script or
animation effects -think of the battery)
— if available, use AJAX to get content
31
33. Touch Devices
Here it is referred to modern devices with a powerful browser like the
iPhone or Android handsets. The touch-sensitive UI offers the possibility
to move more freely within a website. At the same time, it makes it
more complicated to chose one line from a list or any other smaller
element within a page.
If your mobile site complies with the following requirements, any
touch device user shall be able to navigate properly:
— HTML/4.0 Strict
— screensize: 320x480
— GIF, JPEG, PNG (with alpha transparency)
— max. 100kb page size (incl. images, CSS)
— full table
— script is allowed, but not needed
— use CSS, especially the so-called webkit styles for rounded
corners
— if available, use AJAX to get content
— keep the linited battery life in mind
— use a large font size (as example 18px) for links and clickable
lists
— set a default viewport (<meta name = “viewport” content =
“width = device-width”>)
33
34. Learn More — On the Web
If you want to dig deeper and learn more about how to satisfy the
mobile user with your web-based service, check out these websites:
— Mobile Best Practices / W3C
www.w3.org/TR/mobile-bp
— dotMobi Mobile Web Developer‘s Guide / dotMobi
mobiforge.com/starting/story/dotmobi-mobile-web-de-
velopers-guide
— The Wireless Wireless FAQ / Andrea Trasatti and others
www.thewirelessfaq.com
— Global Authoring Practices for the Mobile Web / Luca Passani
www.passani.it/gap
And always remember:
The mobile website is not the small website, it is the mobile one!
Keep it simple.
34
35. Now what – which Environment Should
I Use?
The short and crystal clear answer: it depends.
The longer answer: think about your target users, about their needs,
about their devices and their dataplans. And about your vision and
the requirements for your idea. Remember that you are not necessarily
restricted to a single application environment. A practical approach is
to use the environment that you are most comfortable with and then
move on to other environments for increasing the market reach of
your app. Sometimes it also makes sense to combine different environ-
ments, for example by providing a mobile website for casual users and
a J2ME app for your power users.
35
36. The following table provides a very rough overview about the indi-
vidual strengths and limitations of each application environment.
Green stands for good coverage, yellow for limited and red for bad
coverage of the respective topic:
ce
ol evi
D
De bili e
la fflin
n
of
ra ch
io
lin ity
s
vic ty
at
a
Av / O
In Re
On ctiv
Sp To
nt
me
et
e
e
d
ee
rk
ai
ag
te
Ma
Fr
SMS
BREW
Flash Lite
Starmobi Widgets
Nokia Widsets
Yahoo Go Widgets
Native Blackberry
Native Symbian
iPhone
Windows Mobile
Android
J2ME
Web
36
37. You can also compare application development with web development
in a more general manner:
App Development Web Development
Approval process 2–8 weeks in app stores Instant updates
Portability Complex Easy
Complexity Complex Easy
Monetization Sale, Advertisements, in Advertisements
app purchase
Web development beats application development in many but one
crucial area: monetization. Internet services are mostly free and the
only reliable business model is often advertisements. In contrast, app
stores shine in this area. All stores support charging for application,
the iPhone app store nowadays also supports in app purchases. And of
course you can embed advertisements in your application as well.
If you need to earn money today, it will be easier with an application
unless you want to earn money purely with ads.
37
38. Developer’s Guide
Epilogue
Thanks for reading this initial version of our mobile developer’s guide.
We hope you’ve enjoyed this and we helped you to clarify your options.
Don’t be put down by the difficulties in entering the mobile arena —
once you’re in the water, you can and will swim.
Would you like to contribute to this guide? Please send your feedback
to developers@enough.de!
38