1.1

Abstract

Two primary goals:

1. Create robust backend, decoupling the frontend from the raw API types
2. Fill in the "gaps" in the frontend--core functionality that one expects from an app like this but that is not present

There is also a set of miscellaneous tweaks, optimizations, enhancements, and refinements that should be tackled once the core goals are achieved.

• Unified haptic system (should just be a singleton that provides a consistent haptic "language" rather than instantiating a bunch of one-off haptic generators--ensures consistency across app) (#37, child #56)
• Images
  • Unified image handling (#241)
• Misc
  • Add .webp to list of image extensions (#44)
  • Fix feed loading requests cancelling when scrolling fast (#57)
• Posts
  • Edit (#36, parent #65)
  • Denote and optionally hide read posts (#400, child #40)
• Comments
  • Edit (#35, parent #65)
  • Compact mode (#364)
• Swipey Actions
  • Remove "jiggling" behavior (#16)
• Account switching, instance UX (TBO, child #99, child #115)
• Settings
  • Clean up organization (TBO)
  • Commit to or change icons (#50)
• Remove avatar stroke for certain instances (#47)
• Unread badge on inbox (#217)
• Onboarding
• Guest browsing (#21)
• Images
  • Uploading (#138, #165)
  • Media viewer (#31)
• Unified symbol handling (#48)
• Comments
  • Ability to navigate to comment directly (e.g., tap inbox mention and be taken to the comment, not just the post) (#183)
• Messages
  • Send message not from reply (#622)
• Mask swipey action context menu/drag gesture weirdness as posts do (should just look laggy, not duplicate the view) (#621)
• Clarify currently active instance (#49)
• Quieter user avatar loading animation (#43)
• Hide top and bottom bars on scroll (#38)
• Default launch account (#39)
• Tab tap interactions:
  • Feeds: scroll to top (#42)
  • Search: focus search (#246)
• Show updated time in comments (#156)
• Begin work on middleware layer. Replace APIPostView, HierarchicalComment, and Inbox items with internal middleware types, and update the trackers and views to operate on those (#569, #620).