Loop Logo

Loop

User Journeys

These are made-up scenarios for what a first release of Loop would look like. This does not represent all of the features Loop is planned to have, or any that come after what I think would be feasible for a first launch.

Personas

These are fictional people who each represent a group of users.

Dillan

A university student with aspirations of being a writer. He is part of a study group that is on Loop. He is writing a novel, so he uses Loop as a knowledge-base for the book he is writing, but not the actual book itself. (Tools like Microsoft Word or Google Docs would suit this task better as of the first release of Loop1)

Dillan represents the kind of user who is generally well acquainted with technology, and who have a social purpose for using Loop, in addition to a functional one (the modular knowledge-base).

Sal

A student who attends the same university as Dillan. Both Dillan and Sal are part of the same study group, but Sal doesn’t use Loop that much outside of the group chats.

Sal represents the group of users who would use Loop for a purely social reason.

Evelyn

A mother in a family who all use Loop. They use it as a common task manager, a place for storing their family’s useful links, things to share, and messenger.

Evelyn and her family represent the users who use Loop as a place for collaboration as a group, and as a collection of useful apps.

Mel

A manager at a company. She uses Loop as a personal diary, and as a to-do tracker. Mel represents the group of users who use group as a personal tool, not a social one.

Journeys

Knowledge Base

This section shows how the modular design of blocks can create amazingly well connected wikis.

I. Linking

Context: Dillan is writing about a mythical creature in his novel.

Overall Intention: Dillan wants to connect the creature to an important character in his story.

  1. While typing in the document, Dillan types the “/“ key to start the embed of a block.

  2. He searches for the block (still just by typing) by using “Anthras Medelop by:me” (a query he knows will get a the result) and presses enter. Doing that adds the chosen block within the creature’s, so he can travel between them easily.

II. Reference

Context: Dillan forgot the name of the mythical creature he was writing about. He knows it relates to a certain character in his story.

Overall Intention: Dillan knows he added the character to the creature’s block, so he wants to find it by looking at the character block’s tree.

  1. On the character block’s page, he clicks on the “+9” next to the breadcrumb (“+9” would be the number of blocks besides the ones displayed that are connected to this one).

  2. This expands the breadcrumb to show a tree of where the character block has been used. There he spots the mythical creature’s block.

Study Group

This section shows how messaging and collaboration would work.

Sal is having trouble with some school work. They want to ask the study group for help.

Dillan is working on his side-project, his novel, in Google Doc (while consulting the knowledge-base he made on Loop)

  1. Sal opens the Loop website and goes to the enter page.

  2. They enter their username and password to log in.

  3. On the home page, they click the to page where they can see chats, and click on the study group chat.

  4. Here, the interface changes more like a messenger, but still retains search, block creation, and other parts of the interface that remain the same throughout.

  5. Sal clicks on the message input to send a message (behind the scenes, this makes a Text block) and asks for some help. They offer to pay whoever can tutor them with some credits.

  6. Dillan receives a notification and clicks on it to move to the chat page. He reads the message and wants to help, so he replies that he wants to help.

  7. Within the messenger interface, Dillan clicks on a “+” button and chooses a chat type, to make and send a Chat block.

  8. Dillan clicks on the chat block that is in chat (displayed as the chat’s name & number of messages) to open that one.

  9. As like before, Dillan sends a message asking Sal for more information.

  10. Sal sees this and opens the chat Dillan sent.

  11. They chat/discuss (I’d imagine they would video call of some kind, that is not a Loop feature).

  12. Throughout the discussion, Dillan sends some document blocks he’s made before in the chat, by pressing the “+” button as before but choosing an existing block, and searching for it.

  13. Sal and Dillan conclude talking, and so Sal clicks on Dillan’s profile picture, which brings Dillan’s page. They click on a button to send credits, and type the amount. Sal then clicks a button to confirm the transaction.

  14. Dillan receives the notification for the transaction, and accepts it.

Communal Tasks

This section shows how sending tasks can make for enhanced collaboration between a family.

I. Creation

Context: Evelyn’s family has just gotten on Loop.

Overall Intention: Evelyn wants to make a base for her family’s chores and communal tasks, and a central location to put information about family information, like vacation plans, wish lists, and messaging between the family. (She wants to make a dashboard block2)

  1. Evelyn clicks on the create block button, which opens a place for the block creation. Since the default block type is Text, she clicks on the type button and chooses Dashboard. On the block it says it will cost 5 credits to create because she does not own the type.

  2. She adds some sections to the block, including a title and description. She then confirms its creation.

  3. Using the create block button again, she makes a Chat block in the base. She also adds her family members by typing their usernames.

  4. She buys the Chat block by pressing a button displayed next to the message talked about in step 1.

  5. She confirms with her family that it is set up correctly.

II. Assignment

Context: Evelyn has made a dashboard block for her family.

Overall Intention: Evelyn wants to assign some task blocks to her children as chores.

  1. Evelyn clicks on the create block button, chooses the Task type, and buys the block type.

  2. She types out the text of the chore, and then adds a due date.

  3. She clicks on a button to assign the task to someone by typing their username.

Quick Note

This section shows how individual text blocks would work.

I. Quickly jotting down a note

Context: Dillan is at a park for a walk, and suddenly gets some inspiration for his novel.

Overall Intention: Dillan wants to record a note so that later he can recall what he was thinking.

  1. Dillan takes his phone out and opens the Loop app. This opens up the home screen, where there is a button to make a new block.

  2. He taps the button to make a new block, which then shows him a field for where he can enter his note. (That button changes default type based on location in app, in this case a Text block)

  3. He types out the text, and taps the button to confirm it. (I’m thinking that there could be 2 buttons, “Save + Open” and “Save + Close”)

  4. Dillan is done for now, so he puts his phone away and continues his walk.

Note: it is not in the current scope to develop offline support. Dillan will need cellular data for this.

II. Going back to the note later

Context: Dillan has returned home from his walk, and is at his primary workspace.

Overall Intention: Dillan wants to write more about the idea he had jotted down.

  1. Dillan visits the Loop website on his computer. The home screen displays a Dashboard block, that Dillan has configured to show a couple feeds, including one for recent blocks he’s made. In that section is displayed the note he made before.

  2. He clicks on the memo he made, which opens it’s page. This displays the full text he wrote down, so he can re-read it.

III. Finding a similar note

Context: After re-reading his note, Dillan remembers another note he wrote down before that relates to it.

Overall Intention: Dillan wants to find the note he made before.

  1. Still on the Loop website from the previous action, he starts typing into the search bar (that there should be on every page). Using an in-text filter he searches for only blocks he’s made by including "by:me" into the search.3

  2. He knows it’s text, so he filters it by that also (type:text). This results in a lot of blocks, that he scrolls through to find the one he wants.

  3. In a menu on the block he found (displayed as a card of text) he clicks to associate it to the one he was on.

Now that both of those are connected, whenever he sees one, it’ll show him the other one too.

Morning + Productivity

This section shows how someone would catch up in their morning routine.

I. Checking up with what’s new

Context: Mel wakes up in the morning.

Overall Intention: Mel wants to see if anyone’s posted anything, or if she has any tasks.

  1. Mel opens the Loop app on her phone, which then displays a small & short notification that she has gained a few credits and has a streak of 5 days.

  2. On the homepage Mel sees the first two habits she needs to do today (Jogging and language lessons), and a few Text blocks from some people she had followed.

II. Completing tasks

Context: Mel has finished her morning run.

Overall Intention: Mel wants to mark the run as complete.

  1. She opens the Loop app, where she can see a few tasks. She taps on the check-box to complete it, and it goes away revealing another task.

  2. Mel wants to see what she’s assigned to herself today, so she opens her to-do feed from her home page and scrolls through it to see.

  3. (At this point, it’s pretty much like a regular task-managing app.)

  4. Mel sees a task that she won’t do anymore, so she cancels it.

  5. She presses the button to add a block, and enters the primary text of the block. She also adds a start & due date (Since it’s the to-do page, Loop should know to default to a task block here).

Blog

This section shows how subscribing to a blog would work.

I. Discovery

Context: Browsing around, Evelyn stumbles upon a blog post she really likes.

Overall Intention: Evelyn wants to follow the blog to get updates in her “following” feed.

  1. On the blog post page, she clicks on the breadcrumb to see the tree for what it’s in.

  2. She finds the Blog’s block and goes to it’s page.

  3. She clicks on the follow button to subscribe to that Block’s updates.

II. Feed

Context: Evelyn has followed the Blog, and resumed her day. The next day, she sees a new Blog post in her feed.

No intention, because she just needs to click it to read it.

Onboarding

This section shows how new users can use Loop.

I. Discovery

Context: Evelyn’s friend recommended Loop to her.

Overall Intention: Evelyn wants to see what Loop is and why her friend recommends it.

  1. Evelyn clicks on the link her friend sent her. There, she skims through the home-page to learn what it’s about. There should be many visuals to help explain some of the more complicated concepts, but afterwards Evelyn is intrigued but still a bit confused.

  2. After making an account a tutorial Block is automatically created for her. She plays around with it until she understands Loop’s concepts.

II. Usage

Context: Evelyn knows what Loop is and how it works, but doesn’t quite know what she would use it for.

Overall Intention: Evelyn wants to know what she can do with Loop.

  1. On the home screen, there is a banner for users to get help if they are lost. She clicks it and it brings her the a help block page.

  2. On the page is a few links, one being use-cases. She clicks on that because she wants to know what she could use it for.

  3. She is redirected to a document block full of use cases, so she can understand.

Notes

  1. Loop’s use case is not pdfs. Whenever wanting to print something out, using a tool like Google Docs would be a lot easier. Where Loop fits in is that text can be at the levels of chapters or sections (in the example of a novel). In future (way future, probably) release, a way to create pdf-like things could be possible, but is not in the current scope. Back

  2. A dashboard block would be the type of block the home page is; a place where users can make a custom layout, including blocks and feeds. Feeds are a type of block that generate an interface based on parameters like what to display. Common ones would include a to-do list feed, a recent blocks feed, and a recent chat messages feed. Back

  3. Searching would be one of the most important features of Loop. There will be many blocks of all kinds, so navigation would be extremely important. Many blocks, like the dashboard, would make it easy to navigate, but the easiest would be search. Back