nextcloud / nextcloud/ios

Request: comments rework

Open
#1,626 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Swift
Stars
2.5k
Forks
1k
Avg merge
2d 18h
Merged PRs (30d)
13

Description

Actual behaviour

I just setup a shared folder for family photo sharing. Immediately i was confronted by my family members with the lag of ability for social interaction, which is possible in the Apple shared albums.
As of now the only way to interact is through:

  • Clicking the "more button"
  • Click details
  • Writeout "@Tom" + message (the only way to produce a notification in the other end)
  • The notification on Toms phone is not clickable, so Tom has to:
  • Remember the filename
  • Find the file
  • Click more
  • Click details
  • See the comment
Expected behaviour

There is a whole lot that can be simplified:

  • Show a comment button / indicator in the bottom of each file like in screenshot A
  • Make it so comments triggers a push notification for the owner of the file without having to writeout the name (essential). But might have to do with one of the other repos?
  • Make the push notification (banner) link to the actual file in question and open the comments
  • Dare i say "like button"?

I would be willing to contribute to a developer bounty, but i don't know, if there is a tradition for those in nextcloud?

Screenshots

IMG_9A0B4326E05B-1

Reasoning or why should it be changed/implemented?

Would make the app a lot more appealing for non-tech users.
Also might have been mentioned before? (https://github.com/nextcloud/ios/issues/837)

Environment data

iOS version:
14.4.2

Nextcloud iOS app version:
4.0.1.1

Server operating system:
Armbian, Docker Linuxserver image

Web server:
nginx

Database:
MariaDB

Nextcloud version:
21.0.2

Contributor guide

Open the contributing guide

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.

Research direction

The issue does not name files, tests, or an entry point; start by reviewing the existing comments and notification flows in the iOS app, along with the referenced issue #837. Clarify which request is in scope, then verify that file comments are accessible, notifications identify the file and open its comments, and any agreed interaction has coverage.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.