Mobile Report - Database
Mobile Report - Database
Mobile Report - Database
Prepared By:
Shalaw hoshyar
Muhammad chalak
Muhammad qadr
Mahdi Ali
Asaad aso
Supervisid By:
Mrs.khadija Al_khashab
Contents
Introduction ..................................................................................................................... 1
1. Types of Databases for Mobile Applications: ................................................................... 2
2. Database Examples for Android Studio: .......................................................................... 2
3. Effects of Using Databases in Mobile Apps: ..................................................................... 3
4. Choosing the Best Database for Your Mobile App: ........................................................... 3
References ....................................................................................................................... 4
2
Introduction
Many of the apps you use store data directly on the device. The Clock app
stores your recurring alarms, the Google Maps app saves a list of your
recent searches, and the Contacts app lets you add, edit, and remove your
contacts' information.
1
1. Types of Databases for Mobile Applications:
Mobile app databases play a crucial role in storing and managing data.
Here are the general types:
1. Relational Databases:
o Data is stored in tables with primary and foreign keys to
form relationships.
o Common mobile example: SQLite1.
2. Key-Value Databases:
o Stores information using keys as identifiers with associated
values.
o Used for small bits of data (e.g., UserDefaults in iOS,
SharedPreferences in Android).
3. Object-Oriented Databases:
o Works with complex data objects (as in Swift or Kotlin).
o Executes fast queries with complex data.
o Example: Atlas Device SDKs1.
2
3. Effects of Using Databases in Mobile Apps:
• Good Effects:
o Data Persistence: Store user preferences, profiles, and
cached data.
o Efficient Searches: Organized data enables quick retrieval.
o Security: Safeguard sensitive user and business data.
o Error Detection: Identify inconsistencies and conflicts.
• Bad Effects:
o Complexity: Low-level database APIs require effort and
manual query updates.
o Maintenance Overhead: Updates to data structure can be
time-consuming.
o Boilerplate Code: Conversion between SQL queries and
data objects.
o Performance Impact: Poorly optimized databases can
affect app responsiveness.
3
References