Coding · 3rd Year · Developing Software for Societal Impact · 4.º Período

Prototyping an App for the Community

Begin the development of a software project designed to address a specific social need. Focus on user interface design, historical context of the problem, and accessibility for diverse populations.

TL;DR:This topic marks the beginning of the practical development phase for the community project. Students focus on User Interface (UI) design and accessibility, ensuring their app is inclusive for diverse populations. This aligns with NCCA Learning Outcomes 3.1 and 3.2, which emphasize designing software with the end-user in mind.

• NCCA Curriculum Specifications
• NCCA Coding Short Course LO 3.1
• NCCA Coding Short Course LO 3.2

About This Topic

This topic marks the beginning of the practical development phase for the community project. Students focus on User Interface (UI) design and accessibility, ensuring their app is inclusive for diverse populations. This aligns with NCCA Learning Outcomes 3.1 and 3.2, which emphasize designing software with the end-user in mind.

Prototyping is about more than just aesthetics; it's about functionality and empathy. Students must consider the historical context of the problem they are solving to ensure their solution is culturally relevant. This stage is highly collaborative, benefiting from gallery walks and peer feedback sessions where students can 'test' their paper prototypes on others before writing a single line of code.

Key Questions

1. How does user interface design impact accessibility?
2. What features are essential for a community-focused app?
3. How do we ensure our software is inclusive?

Watch Out for These Misconceptions

Common Misconception

The user interface is just about making the app look pretty.

What to Teach Instead

Explain that UI is about how a user interacts with the app. Use a 'bad design' scavenger hunt to show how poor UI can make a powerful program completely useless.

Common Misconception

I should build the whole app at once.

What to Teach Instead

Teach the value of 'Minimum Viable Product' (MVP). Active discussion about which features are essential helps students avoid getting overwhelmed and ensures they finish a working project for their CBA.

Active Learning Ideas

Gallery Walk

Paper Prototype Testing

Students create 'low-fidelity' prototypes of their app using paper and markers. They display them around the room, and classmates use sticky notes to provide feedback on the layout and ease of use.

40 min·Whole Class

Inquiry Circle

The UI Challenge

Groups are given a specific user (e.g., a tourist with no English or a person with tremors). They must redesign a standard app screen to be usable for that person, explaining their design choices to the class.

35 min·Small Groups

Think-Pair-Share

Feature Prioritization

Students list all the features they want in their app. With a partner, they must use the 'MoSCoW' method (Must have, Should have, Could have, Won't have) to narrow it down to a manageable prototype.

20 min·Pairs

Frequently Asked Questions

What is a 'low-fidelity' prototype?

A low-fidelity prototype is a simple, non-functional sketch of your app, often made on paper. It allows you to test ideas and layouts quickly and cheaply before you spend time writing code. It's a key step in the design thinking process.

How do I ensure my app is inclusive?

Think about diverse users from the start. Use large buttons, high-contrast colors, and clear language. Consider if your app needs an offline mode for people with poor internet or if it can be translated into other languages like Irish or Polish.

How can active learning help with app prototyping?

Active learning, like 'Paper Prototype Testing,' turns the design process into a social conversation. When students see others struggle to find a button on their paper sketch, the need for better UI becomes obvious. This immediate, physical feedback loop is much more effective than a teacher simply explaining design principles.

What features are essential for a community-focused app?

Essential features usually include a clear purpose, an easy way for users to provide or receive information, and accessibility options. For a CBA project, it's better to have two features that work perfectly than ten features that are broken or confusing.