Skip to content

Conversation

@jcytong
Copy link

@jcytong jcytong commented May 13, 2020

Users reported bugs #41, #45 where they were able to copy but not
paste. This is basically a user experience issue where the user didn't
know they had to hold the finger until the copy operation is complete.

However, once a user takes a picture and lift her finger while
the cut command has not completed from the server, the app gets into a state
where it's not recoverable.

The fix proposed uses a single variable "appState" of type AppState to maintain
the app's state. AppState type can be one of:

Init - start up of app
CopyReady - app is ready to copy
PasteReady - app is ready to paste
Busy - app is waiting for results

State variable "pressed" and "pasting" have both been removed.

The fix significantly changes the user experience where it's tap to copy
and then tap to paste.

If we'd like to go back to the hold-then-release UX, we'd need to
discuss on how the UX can be more intuitive.

Fixes #41, #45

cyrildiagne and others added 6 commits May 11, 2020 11:11
Give more flexibility to user by
1. Allowing the use of environment variable AR_CP_SERVER_URL
2. Extract serverUrl from Server.tsx into app.json
The fix proposed uses a single variable "appState" of type AppState to maintain
the app's state. AppState type can be one of:

Init       - start up of app
CopyReady  - app is ready to copy
PasteReady - app is ready to paste
Busy       - app is waiting for results

State variable "pressed" and "pasting" have both been removed.

The fix *significantly changes the user experience* where it's tap to copy
and then tap to paste.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants