Mlem
Mlem copied to clipboard
mormaer
Save Post Feature Integration
Introduction
This proposal focuses on integrating a key functionality, the "Save Post" feature, from the Lemmy website into its iOS client, Mlem.
Requirements
I propose the addition of:
Save Post Feature: Users should be able to save posts for later viewing, a functionality currently available on the Lemmy website.
Discussion
Save Post Feature
The "Save Post" feature allows users to mark posts they find interesting and would like to revisit later. Implementing this feature within Mlem will enhance content accessibility and user experience, aligning the app more closely with the website's functionalities.
What I Need
- Code Adjustments: Add the "Save Post" option in the post options and synchronize it with the user's Lemmy account
- Testing: Ensure the feature's seamless operation and check its impact on overall app performance.
- User Feedback: Collect user feedback after deployment to assess the feature's usefulness and acceptance.
- Iterative Improvements: Based on feedback, make necessary adjustments and improvements over time.
Great idea, in the current mockups, the button is integrated. See here for the button being without background when a post is not saved, and with a background when it is:
This feature is constrained by mlemgroup/mlem#52, which, when integrated, will make this feature possible. @ShadowJonathan can ping us when he's made more progress on the task.
I'm going to get to work implementing the frontend functionality for this--I'll hook it up to a stub for now and connect it to the backend pending mlemgroup/mlem#52
@EricBAndrews great, thank you! Just keep the mock-up I posted earlier in mind, as that is the "official" design into the future. While there will be an overhaul of the comment design later, make sure it fits 👍
@EricBAndrews updated design doc here: https://www.figma.com/file/6TcPi4DD653iWQMaW2drZS/Mlem-Post-View?type=design&node-id=0%3A1&t=yH2fImU62aohlhyk-1
@EricBAndrews could you rebase on master before continuing working on this? The new API client just got merged and I don't want you to run into bad conflicts later and become frustrated.
If you need any specific calls implemented that are not yet in master, please tell me so we can implement them for you ASAP.