Status Post 02: In The Thick of It

Fixing + Identifying Current Bugs

Person(s) Responsible: Danielle + Thomas

Due Date: 2025-10-21

Description/Example(s):

• Link to Excel Tracking

• Thomas and Danielle fixed errors and bugs, some self-corrected once dependencies were updated. Bugs included routing errors (pages not found), database entries (posts) not saving to database and showing on prototype.

Task Flows

Person(s) Responsible: Vidhi + Elizabeth

Due Date: 2025-10-17

Description/Example(s):

• Link to Figma File

• Mapping task flows for current EpiConnect Compared to EPSY

• Through mapping both the flows for EpiConnect and EPSY, our leading competitor, we were able to identify the strengths and weaknesses of each UI, where they differ and how we can improve.

• EpiConnect Original Flow

  • Strengths

    • Emphasis on social features with much of the flow centered around community building.

    • Comprehensive, all in one solution

    • Recognizes that epilepsy management has a significant social/emotional component.

    • Flexible navigation with feature access from multiple entry points.

  • Weaknesses

    • confusing information architecture

    • The flow is sprawling and features are hidden.

    • UI lacks a primary taskclear primary task

    • Visual complexity makes updates and bug fixes difficult.

• Epsy

  • Strengths

    • Clear, linear user joiurney.strengths lie in its linear, clear user journey.

    • Prioritizes clinical data tracking, directing a main focus for users.

    • Connects with Apple Health

    • Dedicated analytics and insights for pattern tracking.

    • Modular structure

  • Weaknesses

    • misses the element of social and peer support epilepsy patients value.

    • Treats epilepsy as clinical and medical, not emotional.

    • Lacks warmth and personality

Desirability Study

Person(s) Responsible: Kaylie + Michelle

Due Date: 2025-10-20

Description/Example(s):

• Link for Desirability Study Results

• Participants tend to use a healthcare app that is simple/intuitive (58%), straightforward and accessible (47%), and clinical/professional (42%)

• An interesting quote: "One that ebbs and flows with my current emotional state. When I am recently post-seizure I feel vulnerable and emotional. As time progresses I need more motivation/fun/light-heartedness to stay positive. After a decent amount of time has passed I’d look for something straight forward and informative on medication advancements."

• People want to feel secure (68%), calm/relaxed (52%), confident and connected (42%) when using a healthcare app

• 63% participants prefer dark mode when using digital apps

• People tend to think of images of brain, lightning bolts, hospitals, and other negative symbols associated with their epilepsy

Location Permissions and weather API

Person(s) Responsible: Shan

Due Date: 2025-10-23

Description/Example(s):

• Link to Github Commit

• Will ask the user once in registration to give the app consent for location access. If they say yes, then the weather API will connect. When logging a seizure or  trigger, it will automatically output the weather associated with the selected date/time for that log. 

Create profile additions: add birthday and add user type

Person(s) Responsible: Danielle

Due Date: 2025-10-27

Description/Example(s):

• Link to Github Branch / commits

• Users under 13 will not be allowed to register. 13-17 will have different features like community restricted, while 18+ accounts will have less safety-related restrictions. Users who indicate they are supporting an individual with epilepsy will have less / different features in comparison to people living with epilepsy (PLWE) 

• Other profile questions like epilepsy type, input for gender (drop down instead of type) to be updated in future onboarding / profile creation flow.