Android, An Enterprise Edition Vision
Number of pages: 96 pages
Release date 15/04/2011
Posted by http://com3elles.com/android2ee-dev
Original title: Android, An Enterprise Edition Vision. French Edition.
Copyright © 2011 by Mathias Séguy
objectives of the book
The new operating system by Google for mobile phones and the new tablets is there. Its reputation is solid, it invades the world of telephony, it is open and offers development tools Java programmers worldwide. It opens the doors of mobile development for all developers objects with minimal cost to the rise in competence. One question arises: are you ready to implement these projects in business?
The objective of this book is very clear: what are the considerations to have when you develop an Android app as a computing professional. What is the test strategy to use? How to sign his application? How to deploy it? How to set up the management of the application lifecycle? How to implement integration continues?
This book focuses its reflection on two things that are essential:
- the know-how
- knowledge design
Concerning the know-how, it is acquired through projects Android whose code is
- purified of any functional considerations,
- extremely accurate (a project for a combo-box, a project for a web kit, a project for...) which explains that the concept associated with the example,.
- very commented and very clear.
A paragraph explains key points of understanding, the code ends the detailed explanation of the concept. This know-how will allow you to put in place all the problems that arise to you.
Concerning knowledge - design, this book explains the key points of the structuring of an Android project. Introduces the elements that form the cornerstone of your project and shows you how to build an application that adheres to these principles and take part in the most efficient way possible. Each of these concepts is highlighted by an Android project whose code has unique aims to present as clearly as possible that concept said.
On reading this book, it seems more reasonable to perform a first quick read, without dwelling on each concept, so as to have a global vision on the various considerations to have when we put in place an Android project. Then the reader refer to the specific chapters that interests him and it wishes to put the concept into practice