Book Image

Fearless Cross-Platform Development with Delphi

By : David Cornelius
Book Image

Fearless Cross-Platform Development with Delphi

By: David Cornelius

Overview of this book

Delphi is a strongly typed, event-driven programming language with a rich ecosystem of frameworks and support tools. It comes with an extensive set of web and database libraries for rapid application development on desktop, mobile, and internet-enabled devices. This book will help you keep up with the latest IDE features and provide a sound foundation of project management and recent language enhancements to take your productivity to the next level. You’ll discover how simple it is to support popular mobile device features such as sensors, cameras, and GPS. The book will help you feel comfortable working with FireMonkey and styles and incorporating 3D user interfaces in new ways. As you advance, you’ll be able to build cross-platform solutions that not only look native but also take advantage of a wide array of device capabilities. You’ll also learn how to use embedded databases, such as SQLite and InterBase ToGo, synchronizing them with your own custom backend servers or modules using the powerful RAD Server engine. The book concludes by sharing tips for testing and deploying your end-to-end application suite for a smooth user experience. By the end of this book, you’ll be able to deliver modern enterprise applications using Delphi confidently.
Table of Contents (22 chapters)
1
Section 1: Programming Power
5
Section 2: Cross-Platform Power
11
Section 3: Mobile Power
15
Section 4: Server Power

Getting permission

One of the first things you'll encounter when trying to use mobile services is that some require express permissions to be granted by the user before allowing your app to access them. That's a good thing—a person's tablet or phone is often a huge collection of personal information. Things such as photos, addresses, emails, passwords, and your current location are not the kind of data that should just be blindly accessed by anyone or any app. Users should be in charge of who gets access to which information.

It used to be that when a new app was being installed, apps would ask the user to confirm all the possible permissions the app would need in order to be installed. These days, the apps are installed, and if and when they need to do something sensitive, that permission is requested and either denied, preventing access for that feature, or approved, allowing the app to proceed. This second method gives the user a more fine-grained control...