1 of 65

Challenges in Client-Side Engineering

CSCI 344: Advanced Web Technologies

Fall 2026

2 of 65

Outline

  • Design
  • Front-end Technologies
  • Short Demo

3 of 65

Design

4 of 65

Norman’s Design Principles

  • Very famous book – came out in the 1980s
  • Shaped the field of product / interaction design
  • Basic idea: designs should be so intuitive that you don’t have to think about them!

5 of 65

Door Quiz

Say out loud what action you use to open the door

“Push” or “Pull”

6 of 65

Door Quiz

7 of 65

Door Quiz

8 of 65

Door Quiz

9 of 65

Door Quiz

10 of 65

Door Quiz

11 of 65

Door Quiz

12 of 65

Door Quiz

13 of 65

Door Quiz

14 of 65

Who cares about everyday things?

  • We make “push” and “pull” decisions every time we interact with computers.
  • We come across badly designed “doors”, and signs don’t change what we do.
  • Norman’s principles apply to all interfaces and interactions

15 of 65

Norman’s Design Principles

  • Affordances: What can the app do?
  • Feedback: System response to user actions
  • Constraints: Limits that prevent incorrect actions
  • Consistency: Uniform design across similar elements
  • System visibility: Showing system status clearly
  • Conceptual models: User’s mental understanding of operation (e.g., “folders”)
  • Natural mappings: Intuitive relationship between controls and results (steering wheel)

16 of 65

The Three Principles That Matter Most for UI

​

  • Affordances - “What can I do?”
    • Visually communicate what actions are possible
    • They are learned
    • Good affordances will allow new users to learn your interface and interactions easily
  • Feedback - "What just happened?"
    • System responds to every action
    • Example: Button states (default, hover, pressed, disabled)
  • Constraints - "What can't I do?"
    • Prevent errors by making wrong actions impossible
    • Example: Grayed-out submit button until form is valid

17 of 65

Affordances of Computer Interfaces

“perceived and actual properties of the thing, primarily those fundamental properties that determine just how the thing could possibly be used”

Affords horizontal scrolling

Affords clicking

Affords closing,

minimizing, maximizing

Affords clicking

Affords dragging to resize window

Affords typing

Source: Nell O’Rourke

18 of 65

Affordances of Computer Interfaces

Affords selecting one or more options

Affords selecting exactly one option

Affords selecting exactly one from a long list of options

Source: Nell O’Rourke

19 of 65

Feedback in Computer Interfaces

“sending back to the user information about what action has actually been done, what result has been accomplished”

Source: Nell O’Rourke

20 of 65

Feedback in Computer Interfaces

“sending back to the user information about what action has actually been done, what result has been accomplished”

Source: Nell O’Rourke

21 of 65

Feedback in Computer Interfaces

“sending back to the user information about what action has actually been done, what result has been accomplished”

Source: Nell O’Rourke

22 of 65

Constraints in Everyday Things

“The world restricts the allowed behavior. The physical properties of objects constrain possible operations.”

Constraints limit insertion direction

Only the right size

pieces fit together

Holes afford inserting fingers

Size of holes gives constraint on possible fingers

Source: Nell O’Rourke

23 of 65

Constraints in Computer Interfaces

Shape of “blocks” enables users to understand how statements, expressions, and events fit together

“The world restricts the allowed behavior. The physical properties of objects constrain possible operations.”

​

Source: Nell O’Rourke

24 of 65

Constraints in Computer Interfaces

“The world restricts the allowed behavior. The physical properties of objects constrain possible operations.”

Constraint on date format; CVV size

Unavailable options grayed out

Source: Nell O’Rourke

25 of 65

Takeaways: Your Job as a Developer

As I build my interface…

  • Is it obvious what users can interact with?
  • Does every action give immediate feedback?
  • Are users prevented from making errors?

26 of 65

Design Tools & Resources

27 of 65

Other Usability Guidelines and Design Patterns

  • Nielsen - Norman Group:
  • Deceptive Designs & Dark Patterns:

28 of 65

Design has become a well-established field

Design principles are fairly well-established, and tech design is its own subfield / specialization within the tech world. Because of this:

  • Many different organizations have codified best practices in interaction design, accessibility, usability, visual design, etc. in UI Kits and design systems.
  • The big idea: instead of making common UX/UI widgets “from scratch,” why not “bootstrap” your website from a baseline set of common widgets and design patterns?

28

29 of 65

Design Systems in Industry

Increasingly, design is becoming separated from implementation in larger tech shops:

  1. Design team works with a baseline “Design System” in Figma (a prototyping tool). This is customized to fit the website’s look-and-feel / brand. Example of Figma
  2. Components and CSS are exported from Figma and “synced” with front-end stylesheet.
  3. So long as the front-end developer is using the correct class names, the design team can work in parallel, with periodic syncing.

29

30 of 65

What is a Design System?

  • A design system is a collection of reusable components, guidelines, and principles that ensure consistency across an organization's digital products.
  • Allows teams to create efficient, scalable, and cohesive user experiences across many different platforms (web, Android, iOS, IoT devices, etc.)

​

30

31 of 65

Why use a Design System?

  • Consistency: Maintains a uniform look and feel.
  • Efficiency: Reduces time spent on repetitive design and development tasks.
  • Scalability: Easy to adapt and maintain across products.
  • Collaboration: Aligns designers and developers with shared tools and language.

31

32 of 65

Core Elements of a Design System

  • UI Components: Buttons, forms, cards.
    • Consistency across like buttons, icons, and cards; uses well-established design and interaction patterns that are already familiar to users
  • Design Tokens: Colors, typography, spacing.
    • A specification that can be imported into an existing framework (and updated easily)
  • Guidelines: Usage rules, accessibility standards.
    • Dos and don’ts for using the system. Example.
  • Patterns and Templates: Reusable layouts and interactions.
    • For common screens that are used across systems (e.g., login page, page not found, etc.)

32

33 of 65

Real World Design Systems

Examples of Famous Design Systems:

  1. Ant Design (Alibaba)
  2. Material Design (Google): Focus on usability and simplicity.
  3. Carbon (IBM): Enterprise-focused, data-heavy design.
  4. Lightning Design System (Salesforce): Components for business applications.

33

34 of 65

Front-End Software Engineering

35 of 65

Introduction to Client-Side Engineering

Client-side engineering comes with unique challenges! To introduce you to some of them, let’s take some inspiration from folks in the trenches of front-end engineering:

​

36 of 65

Discussion Questions

  1. What is front-end engineering? What is UI engineering?
  2. When did it become a distinct subdiscipline of computer programming?
  3. What are some common technologies used in front-end engineering?
  4. What's the best way to get a job in UI engineering?
  5. Is UI engineering easier than other forms of engineering?

​

37 of 65

What is front-end engineering? What is UI engineering?

Front-end engineers make web apps work.

  • Focus on performance, accessibility, and responsive design.
  • Bridges design and backend systems — turning ideas into working interfaces.

UI engineers make them feel right.

  • Focus on component design, interaction patterns, and visual consistency.
  • Collaborates closely with designers to ensure pixel-perfect, reusable UI systems.
  • Often involves design systems, animation, accessibility, and usability testing.

38 of 65

When did front-end become a distinct subdiscipline of computer programming?

Front-end became a distinct programming subdiscipline around 2005–2010, when the browser evolved from a document viewer into a full-fledged application platform.

  • Introduction of AJAX + new JavaScript Language Features
  • Introduction of CSS3 + HTML5 (support for multimedia, animation, etc.)
  • More people accessing and producing content from phones

39 of 65

What are some common technologies used in front-end engineering?

  • ​

40 of 65

What's the best way to get a job in UI engineering?

​

Your answers here…

���Some useful resources that give you a map of “what you ought to know”:

41 of 65

Is UI engineering easier than other forms of programming?

​

  • ​

42 of 65

Additional points to discuss (if not already covered)

  1. Device and Screen Size Variability
  2. Managing State
  3. Network and Latency Issues
  4. Security and Privacy
  5. Accessibility
  6. User Experience (UX) Optimization

43 of 65

Quick HTML, CSS, & �JavaScript Crash Course

44 of 65

Learning Some Client-Side Web Basics

  • For the next two weeks, we’re going to explore some software engineering ideas that are specific to the client
  • To do this, we’re need to learn some HTML, CSS, JavaScript concepts – and some React concepts – in order to make various client-side software engineering principles concrete.

45 of 65

Most web pages use three technologies

HTML

  • controls the content & structure

CSS (Cascading Style Sheets)

  • controls the style, colors, layout, fonts, etc.

JavaScript

  • controls movement and interactivity
  • can communicate with and transmit data to and from servers without refreshing the page
  • can interact with local data stores

45

46 of 65

Document Object Model (DOM)

(n.) How your web browser represents a document (web page), in a way that can be understood by a human and by a computer. Typically, a DOM is created using HTML. Declarative languages like CSS are used to style it, and programming languages like Javascript allow us to change it.

​

Demo. Open your console and type:

> document

47 of 65

DOM Schema

HTML

<html lang="en">�<head>� <title>DOM Example</title>� <meta name="author" content="EECS 130">� <link rel="stylesheet" href="main.css">�</head>��<body>� <main>� <h1>Hello!</h1>� <p>Welcome to this webpage.</p>� </main>�</body>�</html>

​

<html>

<title>

<head>

<body>

<link>

<main>

<h1>

<p>

Hello!

Welcome to this webpage.

<meta>

48 of 65

Intro to HTML

49 of 65

Intro to HTML (Hypertext Markup Language)

HTML is a way of creating web documents using “markup tags”

  1. Each HTML tag has a set of rules that you have to follow to correctly use the tag.
  2. Sometimes, tags need to be nested in a particular way to be understood by your browser.

50 of 65

How the Browser Interprets HTML

HTML File

<html lang="en">�<head>� <title>DOM Example</title>� <meta name="author" content="Sarah V.">� <link rel="stylesheet" href="main.css">�</head>��<body>� <main>� <h1>Hello!</h1>� <p>Welcome to this webpage.</p>� </main>�</body>�</html>

​

Invisible section

(for metadata)

<html>

<title>

<head>

<body>

<link>

<main>

<h1>

<p>

Hello!

Welcome to this webpage.

<meta>

Visible section

(99% of your stuff goes here)

51 of 65

Lots of elements can go inside of the body element

51

Body

<body>

​

​

​

​

​

​

​

​

​

​

​

​

​

​

</body>

​

Image�<img src="??" />

Embedded Video

<iframe src="??"></iframe>

Hyperlink

<a href=”??”>my link</a>

Containers

<div></div>

<span></span>

<nav></nav>

<article></article>

<header></header>

<section></section>

<footer></footer>

Table

<table>

<tr>

<td>Cell 1</td>

<td>Cell 2</td>

</tr>

<tr>

<td>Cell 3</td>

<td>Cell 4</td>

</tr>

</table>

52 of 65

To Learn More about HTML

  • W3Schools
  • CSCI 344 Web Reference
  • MDN (Mozilla Developer Network (Semmy recommended)
  • Google :)

53 of 65

Intro to CSS

54 of 65

CSS Files: Style & Layout

  • Controls the page style & layout
  • Stylesheets can either be internal (within style tags) or external (in a separate *.css file)
  • You can include as many stylesheets as you want!

55 of 65

How to include a stylesheet in your HTML

External stylesheets are stored in a separate *.css

56 of 65

Anatomy of a Stylesheet

body {

color: black;

padding: 1em;

}

.title-bar {

padding: 5px;

font-weight: bold;

}

#profile {

background-color: #ddd;

}

Stylesheets are comprised �of rulesets

56

57 of 65

Anatomy of a Ruleset

​

body {

color: black;

padding: 1em;

}

57

selector

property

value

declaration

58 of 65

Selectors: Most Important Ones

In order to create a client-side app, you need to know how to target / select DOM elements. Three “primary” ways to target elements:

58

Selector

Example

Description

element

p

Selects all <p> elements

#id

#firstname

Selects the element with id=”firstname”

.class

.intro

Selects all elements with class=”intro”

59 of 65

...

1 <body>

2 <div class=”title-bar”>

3 <h1>Welcome, Malik</h1>

4 <img id=”profile” src=”images/pic.png” />

5 <hr>

6 </div>

7 <div>Right

8 <ul>

9 <li>list item 1</li>

10 <li>list item 2</li>

11 <li>list item 3</li>

12 </ul>

13 </div>

14 </body>

...

body {

color: grey;

}

h1, li {

text-transform: uppercase;

display: inline-block;

color: #999999;

}

.title-bar {

padding: 5px;

background-color: #EEEEEE;

}

#profile {

width: 100px;

float: left;

margin-right: 20px;

}

60 of 65

Intro to JavaScript

61 of 65

What is JavaScript?

  1. Initially created as a browser-only language (where the browser is the interpreter)
  2. No strong typing (like Python).
  3. Now used in a variety of different contexts (it can be run anywhere that a JavaScript engine is installed) – e.g., Node.js
  4. Many languages “transpile” to JavaScript (e.g. Dart, TypeScript, CoffeeScript), meaning that you can program in another language, and then run a ‘transpiler’ to convert your code to JavaScript so that your browser can understand it.

61

62 of 65

“Client-Side” JavaScript

What is JavaScript’s job within the browser?

  1. Can respond to user events
  2. Can manipulate the DOM by adding/removing/modifying/deleting elements, attributes, and styling
  3. Can create, read, update, and delete resources from any server (for which it is authorized)
  4. Can do all the computations that an ordinary language can do (but heavy computations are typically delegated to server processes)

62

63 of 65

User Interfaces Make Heavy Use of Event-Driven Programming

  1. An event is an action that your browser can detect and react to. Examples include: mouseover, mouseout, click, scroll, and drag
  2. An event handler is a function that responds to an event

​

What are examples of “events” from your Project 1 course lookup?

63

64 of 65

Selector Demo: Toggle the Lightbulb

Open this link: https://codepen.io/vanwars/pen/GobRrv?editors=0010

Goal: When the user clicks the lightbulb, toggle the image so that it looks like it’s turning on and off.

One Approach:

  1. Create an empty function called “change” to handle the actual toggling functionality.
  2. Create an event handler on the image’s “click” event.
  3. Implement the “change” function so that it modifies the src attribute of the image.

65 of 65