Difference between revisions of "DPS924 Projects Fall 2014"

From CDOT Wiki
Jump to: navigation, search
Line 49: Line 49:
 
** Read "App Developer Best Practices", especially the section on creating "a great app listing page"! [http://developer.android.com/distribute/essentials/best-practices/apps.html]
 
** Read "App Developer Best Practices", especially the section on creating "a great app listing page"! [http://developer.android.com/distribute/essentials/best-practices/apps.html]
 
** Draft a concise description of your Android app.
 
** Draft a concise description of your Android app.
 +
* Submit your project proposal (Word document) at Blackboard. If you are working as a team of 2 people, one submission is sufficient. If you want to receive A or A+, your proposal must be free of spelling errors and address all the questions listed above.
  
 
== [[Android Design Principles and Patterns ]] ==
 
== [[Android Design Principles and Patterns ]] ==

Revision as of 17:07, 10 September 2014

Overview

  • build a useful and interesting Android app
    • real users/clients
  • be innovative
    • market research
    • start-up companies and career opportunities
      • seven Canadian tech startups (2014) [1]
      • 1000 startups [2]
      • startup companies in Toronto [3]
    • startup career in Toronto [4]
    • entrepreneurs and Star-tups (Ontario Centres of Excellence) [5]
  • demonstrate your potentials, creativity, and technical skills

Project Milestones

  • 1.0 [DONE]
    • due: 11:59 pm, September 9 (Tuesday)
    • Task: Identify 1-3 application domains or user/client groups for your project.
    • Example: application domain: Guide for International Students, user group: international students at Seneca
  • 1.1 Project Proposal (Draft Version)
    • due: 11:59 pm, September 23 (Tuesday)
    • requirements posted below
  • 1.2 Project Proposal (Revised Version)
  • 2.0 Design and Implementation of Essential Features.
    • tentative starting date: October 1
  • 2.1 User Feedback & Evaluation.
  • 2.2 Rework the design and implementation.
  • 3.0 Design and Implementation of Additional Features.
  • 3.1 User Feedback & Evaluation.
  • 3.2 Rework the design and implementation.
  • 4.0
    • due: December 3, 2014
    • Project Presentation & Evaluation

Project Proposal: Requirements

Imagine that you are submitting a proposal to a group of investors who may fund your project.

  • What is the business value or possible impact of your project?
  • Who are your users/clients? (You should have at least 3 users and only one of them may be your classmate.)
  • What are the use cases of your Android app? (Include some diagrams if possible.)
  • What is your Testing Environment?
    • configuration of emulators
      • Note: An emulator does not support Google Maps unless you do additional work.
    • configuration of real Android devices (if available)
    • Read the Dashboards to support your choice of the API level. [6]
  • What is the timeline for your project?
  • What resources do you need to complete the project?
    • 1 or 2 developers (names), specific Android device, other devices,...
  • What is the description of your Android app?
    • Read "App Developer Best Practices", especially the section on creating "a great app listing page"! [7]
    • Draft a concise description of your Android app.
  • Submit your project proposal (Word document) at Blackboard. If you are working as a team of 2 people, one submission is sufficient. If you want to receive A or A+, your proposal must be free of spelling errors and address all the questions listed above.

Android Design Principles and Patterns

Android Best Practices

The Android Platform