Data Pulse: examples, uses and sources
Working interfaces showing how structured data informs marketing, design and business operations. Choose an example below to read its purpose, then open the app to try it.
Open the full-screen lab · Structured example manifest
Weather data visualisation for events and operations
A weather app can turn a forecast into useful event-planning information. This Sheffield example combines hourly temperature, rain probability, wind, humidity, cloud, visibility and pressure with daily daylight and UV context.
Choose a day, hour and chart measure to inspect the forecast. Open-Meteo provides the real model data; a labelled fictional sample keeps the interface explorable if the source fails. A production workflow would preserve forecast issue time and the decision made from it.
Data source: Open-Meteo forecast; explicitly labelled fictional fallback
Try this example →An editorial command centre with meaningful measures
An editorial dashboard can connect audience activity, source health and publishing status without treating them as the same measure. This fictional command centre demonstrates how data management supports both the newsroom and the customer-facing design.
Change the sport or measure and inspect a failed feed. Pageviews and outbound clicks remain separate, and a source outage explains which claims must be withheld. In production, panel ownership, refresh timing and comparable reporting windows need explicit definitions.
Data source: Fictional demonstration data
Try this example →Contextual advertising and placement design
A campaign placement can adapt to the article around it and the screen it appears on. The placement studio keeps the creative version and historical performance separate, so an expired advert does not erase the reporting evidence.
Try the football and racing contexts, mobile unit and desktop masthead. An expired creative displays a clear withheld state. Production reporting would store the impression definition, placement, creative version and click event rather than imply a sale.
Data source: Fictional demonstration data
Try this example →Content decisions with visible evidence
A content review interface needs to distinguish a quiet page from a seasonal page or a missing analytics record. The review queue makes those distinctions readable before someone chooses what to keep or replace.
Inspect each sample record, stage a proposal and undo the decision. Missing evidence is not zero performance. A production content-management workflow would preserve the evidence and require the appropriate approval before applying redirects or removals.
Data source: Fictional demonstration data
Try this example →A data-driven restaurant ordering kiosk
A restaurant kiosk is a practical example of structured product information becoming an interactive illustration. Patty quantity, recipe presets, heat and cheese choices control the burger layers and demo price, while the same choices appear in the demo order.
Try a preset, remove chillies or inspect the separate illustration layers. A real product configurator would connect those ingredient IDs to availability, pricing and fulfilment. The demo retains a visible product throughout and does not take payment.
Data source: Fictional demonstration data
Try this example →Product configuration, size and stock
A product page should explain the consequence of a choice. Here, selecting a shoe size changes the illustrated fit ruler, stock message and the size attached to the demo bag.
Try UK 10 to see an unavailable size and choose another size to continue. Product information management can keep the variant, stock and visual state aligned across a shop, kiosk and campaign export. These fit lengths and inventory counts are fictional.
Data source: Fictional demonstration data
Try this example →Event artwork that responds to ticket availability
A booking interface can make event availability visible without turning a low stock figure into a misleading marketing claim. The illustrated capacity grid and ticket total use the same fictional reservation state.
Change the ticket quantity, reserve places and cancel the demo reservation. A production ticketing system would validate capacity on the server and return the confirmed outcome before the animation celebrates a booking.
Data source: Fictional demonstration data
Try this example →Customer booking information from shared records
A customer booking card should make the price, selected quantity and remaining places easy to understand. This workshop interface connects those facts to a compact illustrated availability display.
Reserve and cancel a demo booking to see the totals reconcile. In a live service, the shared record would also supply the confirmation, calendar entry and customer message, with payment and reservation state kept distinct.
Data source: Fictional demonstration data
Try this example →Infrastructure information made understandable
A hosting dashboard can show the relationship between traffic, caching and publishing without claiming infrastructure activity is customer demand. The portal uses separate values for load, cache share and source state.
Switch to a campaign peak and inspect each delivery stage. The same information can inform a technical dashboard and a plain-language service update. The infrastructure and percentages here are simulated.
Data source: Fictional demonstration data
Try this example →Sports statistics as an animated match story
Sports data visualisation works best when the time interval and measure are clear. The fictional match centre uses a score, possession bar and sequential shots chart to build a readable account of the game.
Switch between half time and full time and replay the timeline. A real sports hub would preserve fixture identity, team identity and source status so an animation cannot confuse a partial result with a final score.
Data source: Fictional demonstration data
Try this example →Live sports data across team and event interfaces
A sports hub can use one fixture record across a match summary, team view and screen graphic. This example fetches current ESPN schedules and presents team colours as illustrative shirts, rather than claiming they are verified official kits.
Choose a sport, fixture, home or away colours and an output. Source timestamps and unavailable schedules stay explicit. This separates real sports information from the fictional betting prices elsewhere in the lab.
Data source: ESPN scoreboard with explicit unavailable states
Try this example →Horse-racing visualisation with explicit meaning
The Trackside interface pairs a coded horse visual with a fictional market browser. Its race positions are scripted progress, while its prices belong to a separate sample market. Neither is a prediction.
Advance the race sections, choose a runner and change price format. Expiring the price source disables selections while keeping the race and explanation visible. Production data models should preserve that boundary between event position, market price and source freshness.
Data source: Fictional demonstration data
Try this example →A creative brief driven by structured information
Audience research can inform the message before it becomes artwork. The campaign planner demonstrates an authored rule: a different audience receives a different headline while the event facts stay consistent.
Switch audience and placement to compare the layouts. A repeatable marketing system would retain the approved brief, source record and creative version, then review the actual export rather than assuming a template always fits.
Data source: Fictional demonstration data
Try this example →Turning editorial signals into a usable creative brief
A topical signal is a starting point for an editor, not proof of customer demand. This planning interface shows how an audience choice can inform copy and placement while shared event information remains stable.
Try the maker and business-team briefs. In production, I would retain the source, sample definition and approval alongside the idea. The demonstration uses authored sample copy, not automated claims about an audience.
Data source: Fictional demonstration data
Try this example →Publishing status that explains the next action
A publishing queue turns validation results into something a team can act on. Availability, venue information and artwork each have a readiness state, so an incomplete record does not silently become a customer claim.
Filter to records needing review and refresh the sample. A clear queue displays an explanation and a route back to all records. Production systems should retain who checked the record and which version became publishable.
Data source: Fictional demonstration data
Try this example →Availability data inside a game lobby
Game interface animation should reflect game state. This lobby uses fictional open-place counts to control which worlds can be joined and shows the selected destination as a small illustrated island.
Choose a world, join it and leave again. A full lobby stays visible with an explanation. A production multiplayer service would validate the reservation centrally; the client animation would show the confirmed state.
Data source: Fictional demonstration data
Try this example →A real Sheffield map with a usable place shortlist
A place finder brings real geographic data into a customer interface. These Sheffield locations sit on a Sheffield coordinate diagram, with a list alternative, category filters and links to official visitor information.
Select a map marker or place card, zoom the map and save a stop. Switch to City connections to explore the regional network and straight-line distances from Sheffield. Venue centres are approximate and no live opening or access claim is invented. A production service could connect checked venue records, accessibility information and booking availability.
Data source: Natural Earth and public Sheffield place records
Try this example →Geographic information for council and community services
A public-service map should help people identify a real place and inspect its information. This Sheffield example combines public geographic records with a readable category list and a local shortlist.
Filter libraries, museums or gardens and inspect the selected venue. It is an interface study, not an official council service or live availability feed. A maintained service would need named record owners, review dates and accessible alternatives to the map.
Data source: Natural Earth and public Sheffield place records
Try this example →Campaign reporting with a consistent scale
Marketing reporting needs named measures, comparable periods and clear chart scales. The sample report compares enquiries and qualified enquiries across six weeks without changing the meaning of the vertical axis.
Switch measures and replay the sequential line. A real reporting pipeline would retain event definitions and collection coverage. A rising line can prompt investigation; it does not establish that a particular animation caused the result.
Data source: Fictional demonstration data
Try this example →A sales forecast that shows its assumptions
A funnel can explain the effect of a planning assumption without presenting it as measured performance. This example applies a selected booking rate to a fixed number of qualified enquiries.
Choose another rate to see the projected bookings change. A production forecast would preserve the cohort, time window and assumption version, and compare the eventual result with the original projection.
Data source: Fictional demonstration data
Try this example →One content record across multiple channels
Content modelling can reduce repeated edits across a website, email and venue screen. The library example makes those destinations visible and populates them from the same selected fictional record.
Switch between the workshop and venue record. A live publishing workflow would also carry stable IDs, approval and version history, so a correction can be traced to the material that actually went out.
Data source: Fictional demonstration data
Try this example →A delivery map that traces the customer claim
An infrastructure map becomes useful when it shows where a customer-facing fact came from. This fictional chain connects a source feed, checked record, cache and website.
Select each stage and change traffic or freshness. Delivery load changes the infrastructure view, while an expired record withholds new claims. Production observability should retain source observation time separately from request and cache status.
Data source: Fictional demonstration data
Try this example →Data-led flyers, adverts and screen graphics
Structured campaign content can produce several finished designs without retyping every fact. Output Studio adapts the same approved record into a flyer, display advert, TV graphic or spot storyboard.
Compare a straight creative brief with cinema-inspired wordplay, then switch the campaign and placement. Flyers, adverts, TV graphics and storyboard frames share the same source facts. Holding the record removes customer claims from every format. These are browser proofs, not exported campaign files.
Data source: Fictional demonstration data
Try this example →Connecting marketing with event logistics
A campaign does not stop at the advert. Booking volume can inform declared staffing assumptions, check-in lanes and the arrival message sent to customers.
Change guest numbers, entrance and venue-record status. The route graphic and customer message respond together. This is a fictional planning model, not venue capacity or safety advice; real operating decisions require the appropriate local information.
Data source: Fictional demonstration data
Try this example →Concept films and interface motion
The saved concept film brings together an earlier set of interface studies with an original instrumental score. It illustrates sequential chart growth and data-responsive customer interfaces.
Play the saved concept film to see an earlier set of motion studies. The interactive examples continue to develop independently of this film.
Data source: Fictional demonstration data
Try this example →