Mobile Application Development Syllabus


  1. Pro Git, a free and an excellent way to safely share code, diagrams, and other resources within teams.
  2. Doing Stuff with Web Things.
  3. Optional: Punished by Rewards
    1. Kindle or paperback formats 
    2. iBooks format for apple devices and laptops.


  1. Git. Set up instructions provided in Week 01.
  2. GitHub or BitBucket. Set up instructions provided in Week 01.


CIT 160 - It is expected that you learned and remember the information from CIT 160. If not, during this course you must remediate yourself and relearn that information. However, this will dramatically increase your CIT 261 study time. The instructor will aid you as possible. Do not expect a "review" at the beginning of the course. There is not enough time to review an entire semester's worth of learning.

Course Structure


This course prepares professionals. The instructor is your mentor rather than a lecturer. Having a mentored learning experience is very important to your career. Since exploring technologies to solve previously unsolved problems is what you will eventually do.

In this course you explore technologies such as HTML5, CSS3, and JavaScript, to find, evaluate, and resolve problems. You will also create a single page mobile web application.

You work in team but are responsible for your own learning. You provide evidence of your technology fluency. Additional professionalism evidence is also required.


In this course you prepare for your professional life by becoming more:

CIT 261 outcomes support both the CIT Department and BYU-Idaho student learning outcomes. Please review this Outcomes to CIT 261 Graded Entries map. 

CIT 261 assignments and assessments give you opportunities to achieve these outcomes and assess you against them. If you desire a different set of assessments and assignments, you may propose them (during the first or second week of the semester) to the instructor but your proposal must cover ALL of the course's outcomes in significant ways and to a significant depth. Do not propose a "check list" of do-once and forget activities. These will not be approved.

Learning Model Architecture


Each week you work directly with your team. You must prepare for team meetings. For instance before the scheduled meeting complete assignments received during the previous team meeting, conduct research and write practice code. 

Just as in life, if you do more than fulfill minimum requirements, you will be successful in your team and in the class. Magnify your professional calling.

Teach One Another

Team meetings and a collaborative environment enable each of you to draw from the strengths of others so that your weaknesses can become strengths. This requires effort on the part of both the knower and the learner 'so that both may be edified.'


Pondering is integral to success in this course and life. Weekly, ponder, reflect and then record in a journal. Submit a journal report at the end of the semester.

Proving is also integral to success. Just finding an example of some principle on the web or from your team is insufficient. Explore existing code then generate your own web page to demonstrate how the technologies work and what they do. 

Grading Policies

Course Assessments

This course uses a weighted grading scale.

Assignment Percent of Total Grade
Code Topics 38%
Weekly Self-Reports 4%
Personal Project 26%
Professionalism 22%
Meeting the Schedule 3%
Journal Report 7%

Your overall course grade will be based on the following scale:

Grade Percentage Range
A 100 - 94%
A- 93 - 90%
B+ 89 - 87%
B 86 - 84%
B- 83 - 80%
C+ 79 - 77%
C 76 - 73%
C- 72 - 70%
D 69 - 66%
F 65 - 0%

From the University Catalog

Help and Other Resources

If any technical difficulties arise contact the Help Desk before contacting the instructor.

Help Desk


Phone: (208) 496-1411


Text/SMS (US only): (855) 808-7102