Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Mobile Computing > MC 1,2,3 > Flashcards

MC 1,2,3 Flashcards

1
Q

Smart Mobile Solution

A

Feature + Challenge + Context

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Strategy

A

Competitive Analysis, Research, prototyping, Storytelling and UX.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Mobile First

A

Designing an experience for mobile before any other device

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Smart Mobile Devices

A

5+ Billion Users, 230+Billion app downloads. 93% of internet users on mobile

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

More devices means

A

more people and more consumption

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Multiplatform will…

A

drive Ad and content integration strategies

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Web Applications

A

Accessed via web browser over internet

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Key Characteristics of Web Apps

A

Platform Independent, Requires Internet, Update Automatically

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Native Application

A

Developed for one platform or OS, utilising platform specific OS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Key Characteristics of Native Apps

A

High performance, Device Specific, Works offline

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Cross-Platform Apps

A

Designed to work on multiple platforms with single codebase

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Key Characteristics of Cross Platform Apps

A

Faster Dev Times, Broad Audience, Performance Trade Offs compared to native.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Native Application Design

A

Optimized Performance, Specific IDEs, Best UX cause of features like camera, Higher Cost and Time as need for multiple codebases.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Web Vs Cross Platform

A

Accessibility: Web needs internet
Dev Efficiency: Cross Platform easy as only one codebase needed
Performance: Web apps have improved but still worse performance
UX: Cross platform more consistent experience compared to web apps but not as integrated as native

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Responsive Web Programming

A

Uses fluid grids, flexible images and media queries

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Progressive Web Programming

A

Normal Websites that appear like a mobile app when viewed on mobile. Can add app icon to home screen and can run offline with cache.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Mobile Angular UI

A

Lets you build mobile apps using HTML with inclusion of mobile components like switches, nav bars etc.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Challenges of App Development

A
  • Native or cross-platform approach.
  • Wireless Issues
  • App Design and Implementation
  • Hardware Limitations (screen size, battery, sensors..)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Challenges when designing apps for smart mobile devices

A
  1. Mobile Phones are a main mean of communication
  2. Keep us informed using internet, alarms etc…
  3. Reliable Communication + limited resources
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Mobile Strategy

A
  1. Define your objective (and business objectives)
  2. Select the right mobile environment (i.e app, site …)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Mobile app and site essentials

A
  • Device Specific downloads from marketplaces
  • Leverage mobile device capabilities ex. GPS, cameras
  • Necessitate separate builds for each mobile platform
  • Prioritize dev-based on audience device usage and market trends
  • Mob. Sites in specific serve a distinct audience and purpose compared to mobile apps
  • Ideal for engaging new customers with simple shopping experience
  • Provide on the go services, fundamental info and contact details
22
Q

Strategic Recommendations

A
  • Develop both an app and mobile sources (if sufficient resources)
  • Apps target loyal customers requiring swifter brand interaction
  • Mob sites offer convenience for on the go services and info
23
Q

UX design Investment

A
  • Ensure Mobile sites present clear info and easy data consumption
  • Design for simple adoption and intuitive interaction
  • Maintain robust functionality and performance of apps
24
Q

Usability

A

Don’t trust your own instincts as to what will be easy for people to use

25
Q

Design Patterns

A

Repeatable solution to commonly occurring problems. Description for how to solve a problem that has been tested and validated by different users and can be repeated in many different situations.

26
Q

Best Practices

A
  • Help; Support should be easily available from multiple channels. Use tutorials and help videos. In app content tutorials on added features.
27
Q

What to watch out for

A
  • First Impressions
  • Onboarding
  • Registration
  • Ease of use
  • UI
  • UX
  • Performance
28
Q

Feature (Definition)

A

Means of providing benefits to customer. Distinctive characteristic of good/service. Customers want a benefit and don’t care about features which are sold by every supplier as unique or superior.

29
Q

Context (Definition)

A

Capturing info at a particular instance, using info and applying it; by interacting between human and computer, describing the surrounding facts that add meaning.

In mobile computing, location is used to approximate context and implement context-aware apps. Such as devices that are operational on the move.

30
Q

Design (Definition)

A

Design simple and intuitive, Good design as little as possible, Enough info that allows the user to understand what’s expected of user while offering something useful.

31
Q

Main goal of an app

A

User Engagement

32
Q

What Devs expect from Mobile OS

A
  • best practices of open governance
  • attributes in common with successful open source products such as strong dev tools, and process transparency
  • Equal/fair treatment for developers
33
Q

Android is built on

A

Personal private AND autofill framework

34
Q

10 Steps to create an app

A
  1. Confirm android studio setup
  2. Version control
  3. Access to learning methods
  4. Develop first app
  5. Intro to layouts
  6. Menus
  7. Android manifest
  8. Android lifecycle management
  9. Intents
  10. Activity main screen
35
Q

Layouts (XML or Views)

A
  • Linear Layout: aligns all children in single direction
  • Relative Layout: Displays children in relative position
  • Table Layout: Rows + Columns
  • Absolute Layout: Exact position of children specified
  • Frame Layout: Placeholder for single view
  • List View: List of scrollable items
  • Grid View: 2D Scrollable Grid
36
Q

Menus

A

Fundamental part of an app, offering a familiar way to navigate and interact with features.

37
Q

Handling Menu Selection

A
  • Implement the onOptionsItemSelected(MenuItem item) method to handle menu item clicks
  • Use a switch or if else to distinguish between menu items based on ID
38
Q

Android Manifest

A

The skeleton of your android application, where you declare the essential components and perms your app needs to function within the android ecosystem.

39
Q

Key Components of Android Manifest

A
  • Activities: Define every activity in your app. MainActivity is launcher activity
  • Services: Declare background tasks that operate independently of user interaction
  • Broadcast Receivers: Specify how app responds to various global messages from other apps
  • Content providers: Outline data sharing capabilities, allowing app to share/manage data securely with other apps
  • Permissions: Declare system level data that app requires ex. internet, camera etc.
  • Application ID: Unique ID for app on devices and playstore (com.example.app)
  • API Levels: Define minimum android API level that app supports, ensuring android compatibility.
40
Q

Android Lifecycle

A

Various states in app with different user interaction and system events. Lifecycle encompasses callback methods allowing devs to manage how an activity behaves as user navigates in and out of the app.

41
Q

Key Lifecycle Methods:

A
  • onCreate(): The birth of activity. Initialize components
  • onStart(): when the activity becomes visible to the user
  • onResume(): now the user can interact with the activity
  • onPause(): focus leaves the activity, save transient resources
  • onStop(): Activity no longer visible, release resources or adjust
  • onRestart(): called when the activity is coming back from the stopped state
  • onDestroy(): The final call, cleans up all resources
42
Q

Intent (Definition)

A

Intents are objects used in Android to facilitate communication between components

43
Q

Intent (Purpose)

A

They used for starting activities, services, sending broadcasts and more

44
Q

Explicit Intents

A

Specify the exact component to start and are used in app

45
Q

Implicit Intents

A

Don’t name specific component - instead declare a general action allowing other component apps to handle it. ex. redirect to google maps to show location

46
Q

Activity Main Screen

A

An activity in android represents a single screen with a UI. Fundamental component through which users interact with the app.

47
Q

Activity Main Screen (Lifecycle)

A

Each activity goes through a lifecycle managed by callback methods. These methods allow devs to create, start, pause and destroy activities in an app.

48
Q

Activity Main Screen (Usage)

A

Activities serve as an entry point into interaction with the user. They are used for displaying data, handling input, transition between activities etc.

49
Q

Activity Creation

A

When creating a new project, main activity is created automatically. Represents application starting point.

50
Q

Designing Layout

A
  • UI defined in XML/Layout typically ‘activity_main.xml’
  • Use layout editor to make UI
  • For simple start add TextView ‘HelloWorld’
51
Q

Connecting Layout and Activity

A
  • MainActivity connects to layout through setContentView() method call in the onCreate() lifecycle
  • This connection lets you manipulate UI elements programmatically and handle user interaction

Mobile Computing (4 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions