D799 is a course in WGU's M.S. Computer Science, Human-Computer Interaction specialization.
WGU describes it as blending technical knowledge of sensors, processors, embedded systems, protocols and connectivity with user-centered design principles to create functional, engaging mobile applications, using methods such as personas and usability testing.
The challenge is holding both halves together. Engineers tend to under-develop user research, and designers tend to under-specify technical constraints. The guide lists four competency units, and the course is specific to the HCI specialization.
Course at a Glance
| Item | Details |
|---|---|
| University | Western Governors University (WGU) |
| Course code | D799 |
| Level | Graduate (4 competency units in the guide) |
| Program | M.S. Computer Science, Human-Computer Interaction |
| Subject area | Mobile and ubiquitous computing, UX and privacy |
| Typical work | A mobile application design combining technical and UX analysis |
What D799 Covers
| Competency (summarized) | What it means in practice |
|---|---|
| Analyze foundations of sensing, computing and communication | What sensors and links a device offers and their limits |
| Apply standard user experience principles to a mobile app | Personas, task flows, usability and accessibility |
| Design apps that are scalable and adaptable | Work across different users, contexts and environments |
| Evaluate interaction and synchronisation between devices | How phones, wearables and services stay consistent |
Key Concepts Explained
Sensing and Context
Phones carry sensors such as accelerometers, GPS and microphones. Ubiquitous design uses this context to adapt, but each sensor costs battery and raises privacy questions.
Example: A fitness app can detect movement with the accelerometer, which uses little power, and request GPS only when a run starts. It tells users why location is needed and stops tracking when the run ends.
Personas and Usability Testing
A persona is a realistic description of a user group, built from research rather than invention. Usability testing observes people attempting tasks and records where they struggle.
Example: A persona for a night-shift nurse might note one-handed use and low light. A test task such as "log a medication check" reveals whether buttons are reachable and readable under those conditions.
Multi-Device Synchronisation
When one account spans a phone, a watch and a web page, data must sync reliably, handle offline use and resolve conflicts. Designers decide what happens when two devices change the same item.
Typical Assignments and How to Approach Them
| Task element | What it tests | How to approach it |
|---|---|---|
| Technical analysis | Understanding device capability | List sensors and connectivity used and the constraint each brings |
| User research summary | UX method | Present personas and tasks grounded in stated research |
| Design and prototype description | Applying principles | Describe key screens, flows and accessibility choices |
| Privacy and sync evaluation | Responsible design | State data collected, consent, storage and sync behavior |
Balancing Technical and UX Depth
Aim for even coverage. A simple planning grid keeps either half from dominating.
| Feature | Technical note | UX note |
|---|---|---|
| Location reminders | Geofencing, battery cost | Clear permission wording, easy opt-out |
| Offline mode | Local storage and later sync | Visible status so users trust the data |
| Wearable alerts | Bluetooth link, small screen | Short messages, glanceable design |
Readiness Checklist Before You Submit
Make sure both the technical and the design sides are visible.
| Check | What to confirm |
|---|---|
| Sensors and links analyzed | Capabilities, limits and battery or privacy costs are stated |
| Research shown | Personas and tasks come from stated research |
| Usability planned | You describe how the design will be tested |
| Adaptability covered | Different users and environments are considered |
| Sync explained | Multi-device behavior and conflicts are addressed |
Splitting Your Study Time
The course carries four competency units, so it rewards steady work rather than a single push. Spend the first part on the technical foundations, because the design decisions later depend on knowing what devices can sense and how they connect.
| Stage | Focus |
|---|---|
| Technical foundations | Sensors, processors, protocols and their constraints |
| UX methods | Personas, task flows, usability testing |
| Privacy and ethics | Consent, data minimization, adaptation to environments |
| Drafting | Technical and UX notes side by side for each feature |
| Review | Check each competency has a heading |
Where Students Get Stuck
- Thin user research. Personas and tests are explicit requirements.
- Technology for its own sake. Connect each sensor to a user need.
- Privacy as a footnote. Treat consent and data minimization as design features.
- Ignoring sync conflicts. Explain what happens when devices disagree.
Study Tips for D799
- Use a persona template and fill it from research notes.
- List sensors with power, privacy and accuracy trade-offs.
- Sketch task flows before screens.
- Read D800 alongside, since methods overlap.
How We Help with D799
Send the task, rubric and any draft. A writer with mobile design and engineering experience can prepare a worked model for study, explain UX methods, or review your design for gaps in research and privacy. Our master's assignment help guide describes the process.
GradeEssays is independent of Western Governors University. Model work is for study and reference; your submission must be your own under WGU's academic integrity policy, and no result is promised. Orders are written from scratch with free revisions within the scope of your original request, and a full refund if late.
Make Sense of Your D799 Task
Share the task, rubric and draft. A writer prepares a worked model you can study.
Start My D799 HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
WGU's guide lists it in the M.S. Computer Science, Human-Computer Interaction plan.
Four, according to the guide.
The competencies concern analyzing, applying principles, designing and evaluating. Check your task for any build requirement.
A research-based profile of a typical user group that guides design decisions.
State what data is collected, why, how consent is obtained and how data is protected and limited.
D800 covers HCI principles and user testing methods; D799 applies them to mobile and multi-device systems.