Code Monkey home page Code Monkey logo

appfriendsui's People

Contributors

laeroah avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

kejiat

appfriendsui's Issues

High: Unable to leave a dialog

In the following scenario, users are unable to leave a conversation:

  1. Tapping the "Leave conversation" on the first dialog (either by swiping right on the dialog list or from the Settings screen)
  2. Hitting the iOS Home button
  3. Re-opening the app

After step 1, the dialog disappears but in step 3, the dialog re-appears and in a broken state (unable to send messages - the users get failed message indication, dialog is not named, etc.).

High: Not seeing message title for 1-1 message after tapping push notification

Steps to reproduce:

  1. Device A is logged in, with the app running in the background.
  2. Device B creates a brand new direct message with the user on Device A.
  3. Device B sends a message.
  4. Device A gets a push notification from GC (you can be in the lock screen or home screen, as long as the app isn't open)
  5. Device A's user taps the push notification. The message opens, there is content in the chat view however the title is showing "unknown" instead of the user's name.

Note: if user A navigates back to the convo list and then back to the DM, the title is showing user B's name as expected.

Urgent: media button behavior has changed unexpectedly

  1. Adding Photos & Video: Tapping on the media icon (on the left of the Enter Message field) should bring up an action sheet as it did before. Currently changes keyboard to show 2 icons for taking a picture and accessing photo library

  2. The media icon should be a camera icon rather than a plus icon

Sending a message to massive audience initially reports as having failed to send

When sending a message to a large group (over 242 users), I'm noticing that the message first appears to be in a failed state (red exclamation mark icon). Only after a few seconds, the failed mark is cleared and the Seen By screen is available.
This creates a UX and performance issues with users since they think the message wasn't sent and will continue sending more and more.

I think you might need to change the timeout period for when you display the failed message icon.

Critical: unable to send a message

Sometimes, a message cannot be sent.

In this case, a user was trying to send a message and kept getting an error.
After quitting the app and relaunching, he was able to send a new message although the original failed message would not send. See attached video.
failedmessage.mov.zip

Public API re-vamp

Refactor public api so that the developers have easier time and consistent experience using the SDK.

High: Leaving a 1:1 conversation after sending a message fails

The problem with the 1-1 conversations seems to be that if the user who leaves the message sends the last message, the dialog comes back to the list and is titled as "Private Conversation"; it seems that the last message the leaving user sent is appearing as an unread message, so the api call is pulling the conversation back down to the user who left's device.

Note that this also happens in Android (https://github.com/Hacknocraft/AppFriendsAndroidCore/issues/38)

High: links do not open

Links are no longer clickable and users are forced to copy and paste the link into a browser.

The ideal behavior is that a user taps on the link will get two options:

  1. Open
  2. View the Read Receipt

Medium: UI fixes in the Chat View

Inaccurate Typing Indication

The typing indication is inaccurate: even when users are still typing, the "x is typing" indication disappears a few seconds after the typing has begun.

Medium: UI fixes in Dialog Settings view

  • Text field to name this group isn't really a text field. It should be a text field that the user can type in directly, and saves when the user exits the settings. Currently, tapping the text field gives the user a modal with a text field in it. The grey suggestion text should just be "Name this group" instead of the name of the group. Remove the pencil icon on the right. Zeplink: https://zpl.io/ZEtwFB

  • Fix line weight in "Leave Message" cell / footer. The line style needs to be 0.5px, #A6B4BF. Ref Image:https://www.dropbox.com/s/3g8ysmvl6i9ruqp/WH-14.png?dl=0

  • Copy Change: 'Members' (2nd list item) should say 'Group Members'

  • Copy Change: 'Mute Conversation' (3rd list item) should say 'Mute Push Notifications'

  • Copy Change: 'Leave Conversation' (red outline button) should say 'Leave Message'

High: Support Swift 3.1

Currently it seems that Socket.IO fails to build but there might be other issues.
It would be great if you can update on the ETA for supporting Swift 3.1.

Thanks.

Critical: log out clears all messages

All messages history is cleared when a user logs out. When logging back in, the dialogs are available but the content is empty.
As discussed, we should display the last 100 messages per dialog when logging back in, including media.

High: Unable to Reply to Group Convo

If a user is on their lock screen > then added to a group conversation > then receives a push notification for having been added > the user cannot send a message to the group until they close and reopen the convo

Steps to Recreate:

User A on Device X
User B on Device Y

  1. Log into the app with B on Y, then go to the lock screen
  2. From A on X, create a group convo and include user B
  3. From B on Y, open the push notification for the user being added to that group
  4. From B on Y, try to send a message in that group convo

Notice that the user will not be able to send the message as the app will display the error icon next to the message until the user closes the conversation and reopens it.

Expected Behavior: The user can send a message immediately after opening that initial push notification that alerts them they were added to a new group conversation.

Medium: Read Receipt for Media

The media bubble should be tappable to access Media View.
Media View will have an explicit ‘Seen By’ button within it, as seen below.
screen shot 2017-02-23 at 5 45 01 pm

Critical: Messages weren't delivered to one specific user in the group

Abhinav, Ron, Aman, and I were chatting in our PM group when Abhinav sent two messages that were received by me and Aman, however they never made it to Ron's phone (messages before and after were delivered properly).

The screenshots below show that two messages sent from Abhinav ("nope", guessing you're testing address recognition?") are missing in the second screenshot.

hagit s screenshot

slack for ios upload-1

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.