简体中文
EnglishWebsite review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is This Is Travis?
This Is Travis is the personal portfolio site of a user experience designer, organized around a "Work" section that lists design and UX projects across healthcare, publishing, media, and consumer apps. It functions as a case-study index rather than a product or service: visitors browse project names and tags to understand the designer's range.
The project list shows a few clear clusters:
- Healthcare and patient experience: a motion-centric "flip" site for patients and doctors, an app to improve patient-doctor conversations, and RecoverMe, a chatbot-based injury support app.
- Publishing and reading: ReadUps (a group reading web app with an expiration date), Fortnight Online Journal, NetGalley, BookGlutton social reading, ReadSocial API, and FlatWorld Knowledge.
- Media, games, and installations: Adventures in Changeland for Cisco, an Audible recording marketplace (ACX), a 911 Museum & Memorial kiosk, and Broadcastr.
- Design systems and process: a uAnd Design System and a UX Knowledgedrop presentation.
For a practical read, treat the site as evidence of breadth plus process thinking. If you are hiring or collaborating, start with the two or three projects closest to your own domain, then check whether the tags match the skills you need—for example, "kiosk" and "CUI" for physical or conversational interfaces, "design system" for scale work. If you are a designer yourself, the mix of client work (Cisco, Veeva) and self-directed experiments (Morpheus, Biblionaut, 30 Days of Rain) is the useful signal: it suggests someone who moves between structured product work and narrative or experimental projects.
What types of UX and design projects are showcased in Travis's portfolio?
Travis's portfolio is a working archive of UX and product design projects, with a strong tilt toward healthcare, reading/publishing, and interactive or physical experiences rather than a single specialty.
Project types on the page
- Healthcare and patient communication — a motion-centric flip site for patients and doctors, an app to improve patient–doctor conversations, and RecoverMe, a chatbot-based injury support app.
- Design systems and process — a UX Knowledgedrop presentation and the uAnd Design System, which point to teaching and system-building work rather than only shipped screens.
- Reading, publishing and social reading — ReadUps (a group reading web app with an expiration date), the ReadSocial API (a social reading layer), NetGalley, BookGlutton, Fortnight Online Journal, and FlatWorld Knowledge.
- Games, narrative and interactive media — Adventures in Changeland for Cisco, the Morpheus/Biblionaut interactive narrative, 30 Days of Rain, and interactive narratives.
- Physical, kiosk and voice interfaces — the 911 Museum & Memorial kiosk, LitterBot (a recycling chatbot), and a kiosk-style museum project.
- Enterprise, media and commerce — Audible's ACX recording marketplace, Veeva sales aids, Broadcastr, Globomaestro luxury travel, and earlier work such as Zatso 2000 and SabraCeramics.
What this mix says about fit
The range suggests someone who moves between research, interaction design, content strategy and front-end sensibility. If you are hiring for a healthcare or reading product, the closest reference points are the patient–doctor app, RecoverMe, ReadUps and NetGalley. If you need systems or design-ops help, the uAnd Design System and the UX process presentation are the relevant examples. The kiosk and chatbot work is the better signal for public-space or conversational interfaces.
A practical next step: pick two projects that match your product's constraints — regulated content, kiosk hardware, or social reading — and ask how decisions were made, what was tested, and what shipped.
How does Travis approach user experience design for healthcare applications?
Travis treats healthcare UX as a conversation-design problem first, not a visual one. The portfolio groups projects like a motion-centric flip site for patients and doctors, an app to improve patient–doctor conversations, and a chatbot-based injury support tool under the same UX process heading. The pattern: reduce the clinical exchange to its essential moments, then make those moments legible to both sides of the room.
What that looks like in practice
- Two audiences, one artifact. Patient-facing and clinician-facing views are designed as a pair, so the same content works whether it is read at home or in an exam room.
- Motion as explanation. The flip-site format suggests movement is used to reveal information progressively rather than dumping a full record at once — useful when one party is anxious and the other is time-pressed.
- Conversation as the interface. The chatbot injury-support project points to guided dialogue as the entry point, which suits situations where users cannot articulate a structured query.
- A shared design system underneath. The uAnd design system entry implies reusable components and rules, which matters in healthcare where consistency and predictable behavior reduce error.
Where this approach pays off, and where it does not
| Situation | Fits well | Trade-off |
|---|---|---|
| Patient intake and triage | Guided conversation lowers the blank-page problem | Free-text nuance can be lost if dialogue is too rigid |
| Clinician-facing summaries | Progressive disclosure respects limited attention | Extra taps if the summary is buried too deep |
| Sensitive results | Calm pacing and plain language help comprehension | Motion and reveal effects must never delay urgent information |
A concrete scenario
A patient opens an injury-support tool after a fall. Instead of a form, they get a short exchange: what hurts, when it started, whether they can bear weight. The output is a summary the patient can read and a clinician can scan in seconds. That is the shape Travis's healthcare work points toward — the interface is the handoff, not the database.
Next step
If you are evaluating this kind of work for your own product, ask two questions before anything else: does the design reduce the number of things a patient must understand at once, and does it give the clinician a faster read than the current process? If either answer is no, the visual polish will not save it. You can review the specific projects at This Is Travis.
What design systems has Travis created or contributed to?
Travis's portfolio lists one named design system: uAnd Design System, shown under his Work section. Everything else on the page is project work in UX, product and web design rather than reusable systems.
This Is Travis
What the page actually shows
uAnd Design System is the only entry that is explicitly a system rather than a single product or site. The page gives it no description, so its scope, components or governance are not stated — treat it as a named system he worked on, not a verified set of features.
The remaining entries are individual projects across healthcare, publishing, media and culture, for example:
- Motion-centric flip site for patients and doctors
- App to improve patient-doctor conversations
- Game (Cisco), Audible recording marketplace (ACX), 911 Museum & Memorial kiosk
- RecoverMe, Broadcastr, ReadUps, Fortnight, LitterBot, NetGalley, BookGlutton, FlatWorld Knowledge
These show breadth of applied UX work, but they are deliverables, not systems others would adopt.
How to judge a design system claim
A design system is more than a project list. Useful questions when reviewing any portfolio:
| Signal | Why it matters |
|---|---|
| Named components, tokens or patterns | Shows the system is reusable, not one-off |
| Adoption across teams or products | Distinguishes a real system from a style guide |
| Documentation or contribution model | Indicates whether others can extend it |
| Before/after consistency | Shows the practical payoff |
Practical next step
If you are evaluating Travis for design-system work, ask directly about uAnd: which products adopted it, who maintained it, and what changed for the teams using it. If you are building your own portfolio, follow the same pattern — give each system its own entry with scope, adoption and outcomes, rather than burying it in a project list.
Can Travis's portfolio demonstrate experience with interactive narrative or game design?
Yes. Travis's portfolio includes explicit interactive-narrative and game-design work, alongside adjacent UX projects in healthcare, publishing and cultural institutions.
Interactive narrative and game work
- 30 Days of Rain — an interactive narrative project.
- Interactive Narratives — broader work in interactive storytelling.
- Adventures in Changeland (Cisco) — a game project tagged design, game, UX and web.
- Morpheus, Biblionaut: an Astronaut's Descent into Madness — a code, design, UX and web project with a strong narrative premise.
- Morpheus Biblionaut 2 — a continuation of that project.
Adjacent experience worth noting
- 911 Museum & Memorial Kiosk — kiosk design, where narrative sequencing and physical context matter.
- ReadUps, Fortnight Online Journal, BookGlutton, ReadSocial API and NetGalley — publishing and reading experiences, often built around structured content.
- RecoverMe and LitterBot — chatbot and conversational interface work, useful for branching dialogue and scripted interaction.
- SabraCeramics, Zatso 2000 and uAnd Design System — design and systems work that supports the craft side of interactive projects.
How to read this
The portfolio is not a pure game-development reel. It is a UX and product design portfolio with recurring narrative, reading and conversational threads. If you are evaluating Travis for a narrative game or interactive story role, treat 30 Days of Rain, Interactive Narratives and the Morpheus Biblionaut projects as the core evidence, then check whether each includes playable prototypes, dialogue systems or design documentation rather than only visual case studies.
A practical next step: ask for one project walkthrough covering the branching structure, authoring tools and user testing. That will show whether the work is interactive narrative design specifically, or narrative-themed UX design.
What is Travis's experience with social reading or publishing platforms?
Travis's portfolio shows a sustained focus on social reading and digital publishing. Several projects are explicitly labeled with "publishing," "social reading" or "reading" tags, including ReadUps, ReadSocial, BookGlutton, NetGalley and Fortnight Online Journal. That cluster suggests he has worked across both the reading experience itself and the social layer around books.
What the work covers
- Social reading layers: ReadSocial is described as a "social reading layer," and BookGlutton is tagged "social reading," pointing to features that let readers share, annotate or discuss texts together.
- Group and time-bound reading: ReadUps is a "group reading web app with expiration date," which implies designing around cohorts, deadlines or limited-time access rather than permanent libraries.
- Publishing and discovery: NetGalley and Fortnight Online Journal sit closer to publishing and reader discovery, while FlatWorld Knowledge points to educational or textbook publishing.
- Broader reading-adjacent products: Audible's ACX recording marketplace and the Veeva sales aids show he has also worked on marketplaces and tools that serve authors, narrators or content sellers.
How to read this experience
The pattern is less about any single platform and more about the recurring problem of getting people to read, respond and share in the same place. If you are building a book club tool, a classroom reading app or a publisher's community feature, this is relevant experience: it spans the reader-facing interface, the social mechanics and the publishing-side workflow.
A useful next step is to look at the individual case studies on This Is Travis and ask which of them matches your situation: a synchronous group read, an annotation layer, or a marketplace connecting authors and readers.
NS1
squarespace.com
User reviews (0)