Skip to content

Phase I

Tristen Hale edited this page Nov 11, 2026 · 1 revision

Phase I: Analyzing Users, Competitors, and Initial Designs

Introduction

Have you ever felt like you missed a solar eclipse or a full moon that everyone you know saw? With Skytracker, you won't miss astrological events ever again when you tailor your calendar to the events you don't want to miss.

For this phase, we focused on understanding our potential users and our competitions' apps. From this research, we were able to identify key features that would improve on our competitors' designs.

Methods

Competitive Analysis

We performed a competitive analysis on the following applications that perform similar functions to what Skytracker would do:

For each app, we evaluated the following characteristics…

  • Strengths
  • Weaknesses
  • Quality level
  • Price/Cost
  • Platform

The apps above were chosen because they were some of the first results when searching for “astrological event calendar". Apps that were not chosen to be analysed based on this search either were not viewed due to the scope of the analysis or did not fit our set of criteria. The app needed multiple event types such as moon phases, eclipses, etc, and it needed a way to notify users by allowing them to save events to their calendar, receive banner notifications, etc.

The products also differ in event coverage and supporting features. We observed that AstroCal's focus on moon and planetary events as a limitation, while Stargaze includes aurora and meteor forecasts alongside configurable notifications. Sky Guide offers offline functionality, an interactive sky map, and the ability to view past and future sky conditions. However, it is limited to iOS, and some additional features require payment.

Heuristic Evaluation

We performed a heuristic evaluation on what we agreed our biggest competitor was based on the competitive analysis. From this, we each evaluated AstroCal, and discussed possible discrepancies between our scores (n=3).

We evaluated each of the following characteristics out of 10 points for AstroCal…

  • Visibility of System Status
  • Match between system and the real world
  • User control and freedom
  • Consistency and standards
  • Error prevention
  • Recognition rather than recall
  • Flexibility and efficiency of use
  • Aesthetic and minimalist design
  • Help users recognize, diagnose, and recover from errors
  • Help and documentation

Findings

Competitive Analysis

We found that for most of these apps, they are web applications that require an internet connection to use, with Sky Guide being an exception because it is an IOS app. We also found that the major pain-points involved the limited scope of astrological events and outdated or bad UI designs. However, what we found to be strengths across all of these apps was the use of location-based events and the ability to filter or search for events.

Heuristic Evaluation

We found that AstroCal was a well polished app that allowed for a reasonable amount of user control, while completing the objective of creating an astrological calendar full of different events.

Based on the summary of our evaluation, these are the scores for AstroCal from our findings:

  • 7/10 | Visibility of System Status
    • Most menus and actions have lots of feedback and visible error/OK status.
    • Some points docked for lack of feedback showing which page the user is on, which could have been achieved with tab highlighting.
  • 7/10 | Match between system and the real world
    • In many ways, the app is similar to a physical calendar or planner.
    • Could be improved by allowing the user to view events in a grid-style monthly calendar format.
  • 10/10 | User control and freedom
    • Users can select exactly which categories of events they wish to see using filters.
    • Users can export their events to a standard calendar file (.ics) and import them to their calendar program of choice.
  • 8/10 | Consistency and standards
    • Calendar exports use an accepted standard calendar file format (.ics) used by both Google and Apple.
  • 8/10 | Error prevention
    • The interface is so easy to use, it’s almost impossible to make a mistake.
    • The app avoids errors through simplicity.
  • 7/10 | Recognition rather than recall
    • On first glance, the app looks like a newsfeed with a front page and articles.
    • Most people don’t already know how to save a calendar to their Google/Apple calendar.
  • 9/10 | Flexibility and efficiency of use
    • The ability to customize your feed makes the app very flexible.
    • The simplicity of function and lack of excessive complexity make it very efficient to use
  • 8/10 | Aesthetic and minimalist design
    • The site uses a minimal color pallete with interative elements contrasting to the rest of the site
  • 8/10 | Help users recognize, diagnose, and recover from errors
    • The app works in steps to prevent unnecessary errors like presenting the location search before the events
    • Trying to download an .ics file with no events does not prompt a response from the site
  • 8/10 | Help and documentation
    • The contact page provides a link to email the website's developer if the user has questions.
    • Parts of the site that might be confusing to users are accompanied by brief help text.

Conclusions

From what we have discovered, our app should prioritize the smaller, missing features and an improved UI over our competitors to create a better user experience.

The features we felt need to be added or improved are:

  • Allowing the user to upload and re-save their calendar to update their personal calender
  • Allowing the user to use multiple locations for their events

Future designs should focus on implementing these features such that they allow for better user control without being cumbersome (ie. multiple page redirects) so that users are able to create and update their astrological calendars as needed.

Caveats

Considering all this, it should be noted that the team size and completed research were limited in size and scope due to expected deadlines. These methods also focused heavily on peer review, so there is bias in how each app was evaluated, especially with our team size (n=3). Our team is also new to UX and the processes surrounding UX design, so there may be inaccuracies with how our methods and findings were conducted.

Furthermore, research methods such as surveys, interviews, usability tests, etc. were not conducted due to the scope of the project and expected deadlines. This limits the validity of our claims that “users would want…” because they were not considered in our methods or findings.

Clone this wiki locally