-
Notifications
You must be signed in to change notification settings - Fork 2
Mobile Application Development
Mobile application development is the process of creating software applications that run on a mobile device. A typical mobile application utilizes a network connection to interact with remote computing resources. Therefore, the mobile development process involves creating installable software bundles (code, binaries, assets, etc.), implementing backend services such as data access with an API, and testing the application on target devices.
In the modern smartphone market, there are two dominant platforms: iOS from Apple Inc. and Android from Google. iOS powers Apple's line of iPhone smartphones, while Android is used by various OEMs to build their own smartphones and smart devices. While there are similarities between the two platforms, developing for iOS versus developing for Android requires different software development kits (SDKs) and development toolchains. Developers can target both platforms to reach a wider audience, but they must adapt their applications to each platform's specific requirements and guidelines.
There are four major development approaches when building mobile applications:
These are developed using platform-specific languages and tools, such as Swift or Objective-C for iOS and Java or Kotlin for Android. Native apps offer high performance and access to device-specific features but require separate codebases for each platform.
Developers use frameworks like React Native, Flutter, or Xamarin to write code once and deploy it across multiple platforms. Cross-platform native apps offer code reusability and faster development cycles while maintaining a native-like user experience.
These apps are built using web technologies (HTML, CSS, JavaScript) and wrapped in a native container. Hybrid apps can access device features through plugins and offer a balance between development speed and performance, but they may not provide the same level of user experience as native apps.
PWAs are web applications that use modern web technologies to provide a native app-like experience. They are accessed through a web browser and can work offline, send push notifications, and be installed on the user's device. PWAs offer cross-platform compatibility and easier maintenance but may have limited access to device features compared to native apps.
When choosing the right development approach for their projects, developers consider factors such as the desired user experience, required computing resources and native features, development budget, time targets, and available resources for app maintenance. Each approach has its own advantages and disadvantages, and the choice depends on the specific needs and constraints of the project.
🏠Home
- Third Customer Milestone Report
- RAM
- Requirements
- Mockups
- Sequence Diagrams
- Use Case Diagram
- Class Diagrams
- Scenarios
- User Scenario
- User Manual
- System Manual
- Third Customer Milestone Report
- Second Customer Milestone Report
- First Customer Milestone Report
- RAM
- Requirements
- Mockups
- Sequence Diagrams
- Scenarios
- Use Case Diagram
- Class Diagrams
- Software Quality Plan
- Milestone1 Presentation Scenarios
- Post Creation Page
- User Scenario
- Meeting Notes 10 - Dec 10
- Meeting Notes 9 - Dec 3
- Meeting Notes 8 - Nov 17
- Meeting Notes 7 - Nov 12
- Meeting Notes 6 - Nov 5
- Optional Meeting Notes 1 ‐ Oct 21
- Meeting Notes 5 - Oct 15
- Meeting Notes 4 - Oct 8
- Meeting Notes 3 - Oct 3
- Meeting Notes 2 - Oct 1
- Meeting Notes 1 - Sep 24
- Deniz Ulaş Poyraz
- Eren Donmez
- Ersel Çanakçılı
- Oğuz Kağnıcı
- Onur Çerli
- Yekta Ercul
- Ali Alperen Sönmez
- Huseyin Turker Erdem
- Mehmet Tuluyhan Sozen
352 Material
- Final Milestone Report
- Milestone 2 Report
- RAM
- Use Case Diagram
- Sequence Diagrams
- Class Diagrams
- Requirements
- Elicitation Questions
- Mockups
- Scenarios
- Milestone 1 Report
- Our Favourite Repositories
- Linked Data and SPARQL
- Web Application Development
- API Development and Utilization
- Wikidata and Wikidata API
- Mobile Application Development
- Android Studio
- Git
- Meeting Notes 10 ‐ May 10th
- Meeting Notes 9 ‐ Apr 25th
- Meeting Notes 8 ‐ Apr 21st
- Meeting Notes 7 ‐ Apr 12th
- Meeting Notes 6 ‐ Mar 14th
- Meeting Notes 5 ‐ Mar 11th
- Meeting Notes 4 - Mar 7th
- Meeting Notes 3 - Mar 3rd
- Meeting Notes 2 - Feb 22nd
- Meeting Notes 1 - Feb 18th