Book Image

BlackBerry Java Application Development

Book Image

BlackBerry Java Application Development

Overview of this book

BlackBerry Smartphone was once the domain of jet-setting business users with power suits. Now you can hardly go anywhere without seeing someone using a BlackBerry to check their messages or make a call. It's this kind of explosive growth that makes the BlackBerry ecosystem a great place to develop and market applications through the BlackBerry App World store—this book shows you how to do just that! This step-by-step guide gives you a hands-on experience of developing innovative Java applications for your BlackBerry. With the help of this book, you will learn to build your own applications to illustrate the platform, and the various capabilities that developers can use in their programs. It explores the powers of Blackberry and helps you develop professional and impressive Java applications. The book teaches how to write rich, interactive, and smart BlackBerry applications in Java. It expects the readers to know Java but not Java Mobile or the BlackBerry APIs. We will learn to build rich, interactive, and smart Java applications for the BlackBerry. The book will cover UI programming, data storage, programming network, and internet API apps. As we move on, we will learn more about the BlackBerry's device features, such as messaging, GPS, multimedia, contacts and calendar, and so on.This book also helps you build your own applications to illustrate the platform, and the various capabilities that developers can use in their programs.
Table of Contents (18 chapters)
BlackBerry Java Application Development
Credits
About the Author
Acknowledgement
About the Reviewers
Preface

Laying the ground work


In order to demonstrate the storage techniques appropriately we need a good application to work with. For this chapter, we will start with a journal application. This program is designed to be a simple diary or a journal application that allows you to create entries with some long text and a date. The only problem is that as soon as you exit the application, all of the journal entries are lost because they are not being saved into a permanent storage area.

This is obviously a contrived example, but it isn't too far off from an iterative development cycle where you might be expected to lay out the screen and basic functionality first and add storage or other features later on as the development process continues.