Skip to content

OrganizingSystem_DesignDoc.md

Latest commit

 

History

History
55 lines (42 loc) · 4.15 KB

OrganizingSystem_DesignDoc.md

File metadata and controls

55 lines (42 loc) · 4.15 KB

Addressing issue #1577

Overview

The goal is to develop an interface for categorizing books the library view. The two core systems for organizing books are Groups and Collections. A book can belong to multiple Collections, but only one Group per book.

When designing we should also consider three types of devices: phone, tablet, and desktop (these three are used often and are different enough to be in their own categories). For the this phase of development, I will focus on developing for the tablet. Many tablet developments would also improve the desktop.

As of now, this is what the Library view looks like:

image

Benchmarking

Here is the FigJam I use to store research, you can find the Benchmark board in thie FigJam page.

User Research (Round One) - Key Takeaways

Interviewed 4 Participants on their e-reader uses, I also scored Reddit for some extra infos but it's scarce on there. Please feel free to share your personal experience if you happen to read on your tablet.

  • Touchscreen device users tend to organize their libraries less than Desktop users.
    • Some of them organize on Desktop and read on Tablet/Phone.
    • A majority of them don't have subfolders because they prefer to know everything that is in that folder at first glance.
  • Touchscreen device users (especially the ones on Phones) usually rely on the Currently Reading or the Search section to access their Books instead of the Library view.
  • No mention of tags <-- I'm hypothesizing this should be majorly designed for Desktop people (and Tablet people at one point).

Milestone Issues to be Addressed

  • #1010: A tag system is requested
  • #1667: A shortcut in Library view to easily update progress of the book (see: Goodreads), also could be addressed with a Currently Reading widget
  • #1355: Sorting by series, could be addressed with nested Collection and/or tags

Points that could be addressed in seperate Issues

  • Some features need to be more visible and not hidden in another button (Grid to List, Metadata editor)
  • The default cover template looks confusing for participants (they prefer the Apple Books default covers because they have different colors for each book; one participant said the same grey covers could get very confusing if they have a hundred books without covers)
  • Formating features need to be communicated more efficiently (what is Padding? an average user wouldn't know that. Benchmark Apple Books and Figma for this). Also, remove this feature from Library view, only display it in Reader view.

Possible Exploration

  • A color-coding system using Groups so they seperate Collections and Books rows on the Navbar (to be prototyped)
  • Tagging system
  • Different designs for the Library view
  • Could the cross-device sync of Readest be utilized? (Desktop flow is more organizational and Touchscreen flow is for reading)
  • Concepting a hotkey menu for each Book unit on the Library view to make sure Organizing is possible and smooth on all devices
  • Question: Should the tags be access from the sidebar?

Information Architecture

image

I would argue that we don't need a naming system for Groups (users can just use sub-collections if they need to), Groups can be used as a color-coding system to cluster Collection together on Sidebar.

To-dos (updating)

  • User research (look at people who uses E-readers regularly)
    • Use cases
  • Information architecture of Library view
  • Lo-fi mockups that includes side and Library view to solve the webflow issue
  • Hi-fi mockup: Colored Grouping system (sidebar, Collection carousels)
  • Hi-fi mockup: Book card on Library view (both Grid and List)
  • Hi-fi mockup: Currently Reading widget
  • MVP Library view