Android Studio IDE for Mobile Programming

• IDE stands for Integrated Development Environment
• IDEs are for mobile programming

Android Studio

• An IDE for mobile programming
• Link: https://developer.android.com/studio
• Apply Changes allows pushing code and resource changes to a running app without restarts
• Code templates and GitHub integration provided for app feature building, and sample code importing
• Provides extensive testing tools and frameworks
• Lint tools used for source code checking for programmatic and stylistic errors
• Checks for performance, usability, version compatibility, and other issues
• Features C++ and NDK support
• Built-in support for Google Cloud Platform simplifies integration with Google Cloud Messaging and App Engine

Mobile App Considerations

• Main considerations for mobile app development include the intended utility, app architecture, development principles, target users, and testing
• Intended utility focuses on engagement, productivity, revenue, conversion, and loyalty
• App architecture examines hybrid, native, and mobile web options
• App development principles prioritize user experience, security, management, and hosting
• Target user considerations include consumers (B2C), businesses (B2B), partners (P2B), and employees (B2E)
• Testing includes device testing, performance testing, and various testing scenarios

Intended Utility of a Mobile App

• Aims to increase consumer engagement via richer user experience
• Boosts productivity through streamlined flows
• Drives incremental revenue through increased user stickiness
• Supports customer conversion
• Improves user loyalty through personalized offers

App Architecture

• Select native, hybrid, or web architecture based on requirements
• Middleware is needed for centralized configuration
• Decide on offline versus online capabilities for data storage

App Development Principles

• User experience is enhanced through richer controls and interactive components
• Compatibility across devices and platforms is a key
• Optimize performance for each screen and task
• Implement robust security for data
• Make increased productivity tools available

Target Users

• B2C apps target consumers
• B2B apps target businesses
• P2B apps target partners
• B2E apps target employees

Testing

• Device testing ensures functionality across different devices
• Performance testing ensures optimal speed and efficiency
• Various testing scenarios ensure that all potential issues are handled

Mobile App Challenges

• Diversity of devices and varying technologies means providing optimal experience
• Security requires ensuring data protection during transmission and storage
• User experience requires leveraging device capabilities for engagement
• Design apps to function in areas with varying network conditions, latency and bandwidth
• Ensuring compliance with diverse standards, OS, mobile platforms, and devices is essential

Application Types

• PC Based Applications
• Web Based Applications
• Mobile Based Applications

PC Based Applications

• PC Software developed to run on specific operating systems and hardware
• Were the initial applications used in early software development
• Two Types: Standalone and Client-server

Standalone PC Applications

• Independent software programs that run on an operating system
• Do not use network resources or support multi-user mode
• Examples include word processors, calculators, and media players
• Have a user friendly interface for interaction

Client Server Applications

• Each PC has client software connecting to a centralized server
• Client program uses input from the end user and submits these details to the server which has dedicated session
• Also known as "thick clients"
• Examples: Database software, networked games, banking software, and network file systems

Web Based Applications

• Internet-enabled that render on desktop browsers
• Follow layered Model-View-Controller (MVC) architecture
• Supports loose coupling
• Flexible modular components

Typical MVC Architecture

• M: Data layer is the model layer
• V: Presentation layer is the View layer
• C: Business layer is the controller layer

Presentation Layer (View Layer)

• User experience (UX) components like portlets, widgets, and User Interface (UI) modules
• Uses JavaScript components to build the UI modules
• The UI modules render displays
• View components communicate with back end services which uses Representational State Transfer (REST) based light weight services.

Business Layer (Controller Layer)

• Consists of business components implementing business logic and rules
• Also includes rules engine, search, business objects, and workflows
• Utilizes Business Process Management (BPM) and caching frameworks
• All business modules share services to the presentation layer

Data Layer (Model Layer)

• Consists of persistence handling components
  • Database access components
  • Data access objects (DAO), query components
  • Object Rational Mapping (ORM) frameworks
• Besides these layers, there are also security components responsible for authentication and authorization

N-tier Enterprise Web Application

• Presentation Layer
• Web Content Management Layer
• E-commerce Layer
• Integration (Services) Layer
• Security Layer

Presentation Layer Components

• Personalization: Role-based access and fine-grained controls for tailored user experiences
• Widgets: jQuery based client-side widgets enhance user experience and page performance
• Multi-device support: Uses responsive design and device recognition to support various mobile devices
• Page layouts: Flexible layouts for web pages
• Information architecture and navigation models: Use context menus, bread crumbs, and site maps for web site navigation

Web Content Management Layer

• Consists of modules for
  • Content authoring using templates
  • Content tagging with metadata and tags
  • Content publishing to various targets and formats
  • Asset management of digital assets and multimedia files
  • Workflow for managing content approval, publishing, and updates

E-commerce Layer

• Modules typically consist of: -Catalog and order management -Shopping cart, promotion, cross-selling, up-selling, and product management

Integration (or Services) Layer

• Integrates external systems through a business service layer
• Utilizes Service Bus Architecture where middleware acts as a service bus
• Links multiple applications together with central service
• Service bus becomes a data interchange point
• Manages communication with each peripheral application independently
• Service invocations are done through an Enterprise Service Bus (ESB) layer
• Java Messaging System (JMS) component supports send and receive messages to the ESB message destination
• Application/System services are developed and exposed to the ESB layer

Enterprise Service Bus (ESB)

• Fundamentally an architecture for integrating numerous applications
• A set of rules and principles used over bus-like infrastructure
• ESB products build architecture but vary in approach and capabilities
• Integration uses communication bus to connect applications
• Communication bus enable each application to talk to the bus

Security Layer

• Consists of modules related to
  • Authentication
  • Authorization
  • Single sign on

Mobile App Development Stages

• Development goes from:
  • Embedded Systems
  • Device Specific Apps
  • OS Specific Apps
  • Cloud Based Apps.

Evolution of application function

• Embedded systems: limited functionality, includes calculators, etc.
• Device specific apps: category includes device specific games and other utility apps
• OS specific apps:Operating system specific, includes games and media players
• Cloud based apps: Category includes always available cloud-based apps.

Mobile App vs Web Application Criteria

• User intuitive features: mobile apps utilize more phone features (camera, GPS, notifications)
• Interactivity: mobile apps have higher interactivity, using touch interface
• Applicability: Mobile apps are preferred for gaming and location-specific context
• Personalization: Mobile apps provide higher degree of personalization using various context parameters like location and history.
• Common Use: Mobile is preferable for gaming, social media and location services