MECM20003 Chap.9 App Design, Datafication and Disconnection
App Design, Datafication and Disconnection
Define critical app studies
The course material gives this chapter a concrete anchor: Weeks 10 to 12 connect app analysis and design with tracking, analytics and disconnection.
That critical app studies anchor controls how datafication is explained and how digital disconnection is tested in changed practice.
App Design, Datafication and Disconnection asks how critical app studies, datafication and digital disconnection change the interpretation of a text, case, institution or public problem.
The chapter's practical task is to design an app while evaluating data, access, infrastructure and disconnection; that requires an argument, not a list of themes.
Define critical app studies at the scale of the chosen case. Identify who uses the category, what it makes visible and what it may conceal.
This prevents the critical app studies definition from floating above the evidence as an interchangeable opening paragraph.
Trace datafication
Use datafication to explain the relationship between the case and the claim.
Quote, describe or compare only the evidence that advances datafication, and make the inferential step visible instead of assuming the example speaks for itself.
Bring digital disconnection in as a second lens or consequence. The digital disconnection reading may deepen the first account, expose a conflict or show why another audience would interpret the same material differently.
The comparison should change the conclusion, not simply add another term.
To design an app while evaluating data, access, infrastructure and disconnection, build each paragraph around one contested move: claim, specific evidence, explanation and qualification.
A digital disconnection counter-reading is strongest when it identifies exactly which premise or piece of evidence it changes.
Test with digital disconnection
Make an evidence table for critical app studies with four columns: passage, image, event or institutional fact; the concept it activates; the inference drawn; and a plausible competing reading.
Place critical app studies and datafication in separate rows before combining them. This keeps datafication interpretation anchored in specific material and shows where disagreement enters the argument.
Test the scale of every claim. A detail involving critical app studies may support an argument about one text, group or moment without supporting a claim about an entire culture or institution.
Use digital disconnection to decide whether the evidence should be widened, narrowed or compared with a counter-case before the paragraph reaches its conclusion.
For timed revision in MECM20003, write a one-sentence thesis for the application — design an app while evaluating data, access, infrastructure and disconnection — then list the minimum evidence needed to defend it.
Add one digital disconnection objection that would matter if true and revise the thesis so it survives.
The exercise trains digital disconnection argument selection and qualification rather than a memorised inventory of course terms.
Transfer to App Design, Datafication and Disconnection
A complete response should make the task visible before the detail: identify what must be decided, define the relevant terms, connect the evidence to datafication, and use digital disconnection to test the result.
The final sentence about digital disconnection should answer the question actually asked rather than merely repeat the topic.
The controlling limit is specific: a polished prototype can still reproduce surveillance, exclusion or compulsory connection.
Keep that digital disconnection limit beside the worked example, because it separates a careful MECM20003 answer from one that sounds confident but claims more than the task or evidence supports.
For revision, retrieve critical app studies, datafication and digital disconnection without notes, explain their relationship aloud, then complete a changed version of the application: design an app while evaluating data, access, infrastructure and disconnection.
Record the first failed datafication reasoning move and repair it before attempting another case.
What this chapter covers
- 01
Critical app studies
- 02
Datafication
- 03
Digital disconnection
- 04
Applying critical app studies
- 05
Limits of datafication and digital disconnection
App Design, Datafication and Disconnection application
- 1Define the case-specific object and objective.
- 1Trace the main mechanism using the evidence supplied.
- 1Test a plausible alternative or changed condition.
- 1State a qualified action or interpretation.
Key terms
- Critical app studies
- Analysis of apps through interfaces, infrastructures, political economy and everyday use. This chapter uses the concept when students design an app while evaluating data, access, infrastructure and disconnection. Use this definition when the task is to design an app while evaluating data, access, infrastructure and disconnection.
- Datafication
- Conversion of activities and relations into data that can be measured, analysed and acted upon. It helps explain the reasoning required to design an app while evaluating data, access, infrastructure and disconnection. Use this definition when the task is to design an app while evaluating data, access, infrastructure and disconnection.
- Digital disconnection
- Practices of limiting or refusing connectivity and the meanings attached to doing so. Its limit matters because a polished prototype can still reproduce surveillance, exclusion or compulsory connection. Use this definition when the task is to design an app while evaluating data, access, infrastructure and disconnection.
App Design, Datafication and Disconnection FAQ
Which constraints shape the work needed to design an app while evaluating data, access, infrastructure and disconnection?
Design an app while evaluating data, access, infrastructure and disconnection. Weeks 10 to 12 connect app analysis and design with tracking, analytics and disconnection. Analysis of apps through interfaces, infrastructures, political economy and everyday use. This chapter uses the concept when students design an app while evaluating data, access, infrastructure and disconnection.
Can a polished prototype still reproduce surveillance, exclusion or compulsory connection?
A polished prototype can still reproduce surveillance, exclusion or compulsory connection. Conversion of activities and relations into data that can be measured, analysed and acted upon. It helps explain the reasoning required to design an app while evaluating data, access, infrastructure and disconnection.
If a data permission were removed, how should a student redesign the value proposition?
Explain why each data field is necessary, offer meaningful control and non-tracked participation, and test whether motivation depends on surveillance or social pressure. A polished prototype can still reproduce surveillance, exclusion or compulsory connection.
Assessment move
Reconstruct the relationship among critical app studies, datafication and digital disconnection; complete the chapter application without notes; then test the result against this limit: a polished prototype can still reproduce surveillance, exclusion or compulsory connection.
Working through App Design, Datafication and Disconnection in MECM20003? Sia is AskSia’s AI Media and Communications tutor — ask any MECM20003 App Design, Datafication and Disconnection question and get a clear, step-by-step explanation grounded in how MECM20003 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
