Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feedback points from previous semester

Open
#31 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
swift
Domain
mobile

Research direction

The issue lists several UI and navigation concerns across the app but names no files, tests, or entry points. Start by reproducing each item on the relevant screens, using the Binghamton screenshot for the image-loading problem. Done means the listed scrolling, sizing, countdown, navigation, empty-state, pagination, image, and location behaviors have been addressed and checked.

Written by the indexing model from the issue text.

Description

Comments received last semester from Noah (prev team lead):

  • Horizontal scrolls should have the padding within them, since the padding is on the parent it looks weird when ur scrolling
  • the tab navigator bar is also super tall, use the native hieight
  • The details countdown doesn’t tick in realtime and the hourglass icon could prolly be smaller
  • Are the detail views native view controllers? The headers don’t look native and I can’t swipe to go back, probably a small fix to make it feel more native
  • Empty states on the home screen don’t have bottom padding
  • Nice job on pagination - probably don’t need a “load more” button, you can just load the next page when the user scrolls to end
    some images/logos aren’t loading - see the Binghamton screenshot
  • A lot of game locations say “n/a”, maybe just hide it for that game if there’s not enough data
Dominant language
Swift
Stars
1
Forks
2
Avg merge
3d 18h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cuappdev/score-ios

All issues in cuappdev/score-ios

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.