MECM30002 Chap.3 Platforms and Digital Life
Platforms and Digital Life
Platforms are not neutral spaces where social life simply happens. They provide programmable infrastructures, organise interactions, extract data and connect users to markets and institutions. Everyday actions become inputs for classification, prediction and monetisation, while affordances and ranking systems shape what becomes visible.
The chapter follows a feedback loop from user activity to data extraction, prediction, monetisation and redesigned experience. It also distinguishes surveillance from sousveillance and asks how users adapt, resist or redirect platform functions. The analytical aim is neither to deny agency nor to treat design as destiny.
It is to explain how choices are structured by technical features, business objectives and institutional power.
What this chapter covers
- 01
Platforms as programmable infrastructures
- 02
Affordances and structured choice
- 03
Data extraction and prediction
- 04
Monetisation and feedback
- 05
Surveillance and sousveillance
- 06
User adaptation and platform power
Worked example · free
Audit a recommendation loop
- 1Identify the user activities converted into data.
- 1Explain how classification supports prediction.
- 1Connect prediction to the platform objective.
- 1Show how ranking changes later activity.
- 1Name a limit or user adaptation.
Key terms
- Platform
- A programmable infrastructure that organises interactions among users, services and markets.
- Affordance
- A possibility for action created through the relation between design and user context.
- Data extraction
- The recording and conversion of activity into inputs for institutional use.
- Surveillance
- Systematic observation and classification used to manage or influence conduct.
- Sousveillance
- Observation from below, often used to document authorities or powerful actors.
Platforms and Digital Life FAQ
Are platforms just digital intermediaries?
They mediate interactions, but they also set rules, design interfaces, collect data and determine visibility. Those capacities make platforms institutional actors. Analyse what the platform controls and which dependencies remain outside it, including infrastructure, regulators and user communities.
Does an affordance cause behaviour?
No. An affordance makes an action possible, easier or more legible for a particular user in a context. Explain the social expectation, interface cue or incentive that gives it force, and preserve variation in how people interpret or resist it.
How is data part of everyday life?
Ordinary actions such as pausing, clicking, travelling or messaging can be recorded and converted into categories. Those categories shape prediction and future visibility. The analytical task is to trace the chain without assuming that every collected signal is accurate or equally consequential.
Assessment move
Draw a four-stage feedback loop for every platform case: activity, extraction, prediction and intervention. Under activity, name the concrete user action. Under extraction, identify the record produced. Under prediction, state the category or expectation. Under intervention, describe the ranking, prompt, price or rule shown to the user.
Add the institutional objective beside the loop so that recommendation is not treated as a purely technical process. Then mark one point where users can adapt and one point where regulation or infrastructure can intervene. Practise distinguishing affordance from outcome: the feature invites or structures action, while social context and user goals shape whether the action occurs.
For surveillance cases, identify the observer, the observed, the purpose, the data and the decision. For sousveillance, ask whether recording changes accountability or merely creates more circulation. Build essay paragraphs around a mechanism in the loop and support each link with evidence. End with a limit about accuracy, variation or unseen dependencies. Keep a platform claim audit beside the loop.
Copy the service's public promise, then list the technical operation, revenue relation and responsibility that the promise leaves unstated. Locate a different source for each layer instead of asking one privacy policy or interface screenshot to prove everything. Rework the case from the position of a user, creator, advertiser and moderator; each position reveals a different dependency and decision right.
When a paragraph says the algorithm acts, replace that noun with the classification, ranking or allocation actually occurring and identify who chose its objective. Compare one intended use with one user appropriation to preserve agency without treating resistance as equality.
During revision, check that data is never equated automatically with accurate preference and that a measured action is not presented as a stable identity. Finish with an accountability sentence naming the actor able to test, explain or change the outcome. For a final drill, take one recommendation and trace the minimum evidence needed at every step from activity to record, classification, prediction and intervention.
Mark where the platform could have selected a different objective. Then add a user adaptation and an external constraint. This creates a compact paragraph plan that preserves both structured choice and institutional asymmetry. Retain the original platform promise in your notes so the conclusion can answer it directly rather than drifting into general criticism.
