Please enable JavaScript.
Coggle requires JavaScript to display documents.
CH1 - Coggle Diagram
CH1
Business Models for Mobile Apps
Freemium
Free but users have to pay for additional features
Must be attractive
Advertisement-based
display advertisements on the screen as users interact with the
applications.
for revenue generation is more effective if the applications are used for
relatively long periods of time.
Transaction-based
charge the users either per transaction
A flat fee or a percentage of
the transaction value or similar
usually applied for business and financial apps such as mobile wallets
Fee-based
require the users to pay for downloading and installing the application
probability of users buying such an app increases if it provides
outstanding features or usability, or when competing applications are not available
enterprise applications
Do not charge their users
Banks or e-commerce
developed for
internal use within the organization and provide an interface to the services provided
Types of Mobile Applications
Native
developed using platform specific SDKs
downloaded, installed and
updated from supplier stores.
may need testing on all supported devices
provide better performance, can fully utilize platform features
Browser-Based
accessed through a mobile browser
four main ways to create Browser-Based Apps
Mobile Specific versions of websites and Apps(m.)
when a mobile browser addresses the application, a mobile version of the application is provided. (m.facebook.com)
Responsive web app
ensure that the design adjusts to the form factor and screen size,
usually expressed as view ports
(The same view is kept for all screen sizes)
Adaptive web apps
predefined sizes
There are different
designs for these sizes and the features available to the user are often adjustable.
Progressive web apps
allow shortcuts of specific web pages to be created on the mobile
home screen
Appear like native apps and sometimes even can work offline.
-created using common web technologies
-not be as feature-rich
as native or hybrid apps
-access to mobile sensors is also limited.
Hybrid
combination of native app and web app
native app wrapper
which contains a web view to run a web application inside of a native app
-downloaded from supplier stores and can access all of the device features.
Mobile Application Architecture
4 Decisions
Client-side architecture Thin/Fat
Thin
-Do NOT contain App Code
customized to the device and make minimal
use of mobile operating system features
-Use the web browser as the front-end
and JS for implementing client-side logic
Fat
May have multiple layers of application code and may use mobile
operating system features
Native or Hybrid applications
Data synchronization between Client & Server
Continues Mode -> data gets transferred as soon as it is submitted
Store-and-forward -> data may be stored locally before being transferred,
especially when no connectivity is available
Data Transfer Approaches
Synchronous
performed when the calling function waits for the called
function to complete before returning
Asynchronous
performed when the called server function returns immediately, processes the data in the background and calls back the calling client function once it completes the task
Server-side architecture Single/Multi-Tier
Single-tier
monolithic and have all servers on the same machine
less scalable and harder to secure
Multi-tier
spread server-side components across various units
2 Tier -> separated web & DB Servers
3 Tier -> Web + DB + App Server
Multi-Tier Allows separation of responsibilities, provide database specialization ,better flexibility, scalability
and security.
Connection type
WI-FI- 3,4,5G
Three Methods
Never-connected apps
Work Offline, NO need to be connected (Calculator)
Always-connected
require a permanent network connection
All mobile web applications fall into this category
Partially-connected
require a connection for tasks such as data transfer
can
operate for long periods of time without connection
Stackholers
Manufacturers
Platform Providers
OS Providers
Market Data Providers
Tool Providers
Dev & Testers
Mobile Analytics Data user for selecting Device Portfolio