Skip to content
This repository has been archived by the owner on May 11, 2020. It is now read-only.

Implementation of voice call message activation #71

Open
maruthi12 opened this issue Dec 20, 2014 · 25 comments
Open

Implementation of voice call message activation #71

maruthi12 opened this issue Dec 20, 2014 · 25 comments
Assignees
Milestone

Comments

@maruthi12
Copy link

hey guys.......i tried to register using sms for more than 10 times....and i 'm fed up as the code is not received.......can u add the voice code registering feature.......

@duesenfranz
Copy link
Contributor

@willyaranda I'd like to work on this, but I guess it might clash with #64.

Can you give a rough estimation about #64? ☀️

@willyaranda
Copy link
Member

I want to merge today (with maybe some changes).

Please, work on top of your PR.

@duesenfranz duesenfranz self-assigned this Dec 20, 2014
@duesenfranz
Copy link
Contributor

I would propose that a button appears on the number-confirmation-screen after an error occurs, and additionally to the code-confirmation-screen.

For the code-confirmation-screen: should the button be instantly clickable or just after some timeout?
(this is how connectA2 handles this)

@willyaranda
Copy link
Member

@duesenfranz I think it's better on the PIN screen. With something like: "If you do not receive the code in the following 5 minutes, click here, and WhatsApp will call you with the PIN".

@duesenfranz
Copy link
Contributor

@willyaranda thats what I meant with code-confirmation-screen :)
But I'd say that instead of such a long text, we have a timer / progress bar or something?

@willyaranda
Copy link
Member

Yeah, that is interesting...

A countdown from 1 minute, and then enable a "Call me" button.

@duesenfranz
Copy link
Contributor

Maybe something like the progress bar on this page above or below the button?

Edit: like this: progress bar

@willyaranda
Copy link
Member

I would prefer a simple countdown

@duesenfranz
Copy link
Contributor

Just a small update:

I got it running with this commit, it's not ready for a PR yet.

(note that this requires this change to be applied to coseme)

How it would look right now:
waitforcall
callready
callrequested

@duesenfranz
Copy link
Contributor

@willyaranda sorry I didn't see your comment yet...

Do you mean within the button, instead of "Call me!"? Or below the button?

@Timmaks
Copy link
Contributor

Timmaks commented Dec 22, 2014

@duesenfranz i like your design with the progress bar

@willyaranda
Copy link
Member

Could you please put a horizontal bar or something to separate both parts of the screen? We understand what is that progress bar, but maybe a user doesn't :)

@duesenfranz
Copy link
Contributor

@Timmaks @willyaranda

Yeah I agree that it isn't clear they belong together the way it is, what about this:
waitforcall2
callready2

@willyaranda
Copy link
Member

Yeah, better

@Timmaks
Copy link
Contributor

Timmaks commented Dec 22, 2014

I don't like the bar combined with the button. A2 has a countdown screen with a time in seconds, does you know where that time comes from?

The progress bar in your first design is in my opinion related to the wait time of receiving the sms. If that doesn't come you can request a call.

@Timmaks
Copy link
Contributor

Timmaks commented Dec 22, 2014

But the opinion of @willyaranda preponderate :)

@willyaranda
Copy link
Member

@Timmaks no :) I'm not a UX/UI expert

on Android, there is a 5 minute countdown (with a progress bar?), maybe ConnectA2 do that.

@duesenfranz
Copy link
Contributor

@Timmaks A2 also has a simple countdown from (I think) two minutes.

WA only lets you request a call after ~2 minutes, otherwise it fails with too_early.

@willyaranda
I also can include a timer if you want, that would look something like this I guess:
waitforcall_withtimer

That said, I like it much more without the timer, it seems overloaded to me otherwise ☀️

@willyaranda willyaranda modified the milestone: 1.8.0 Dec 24, 2014
@duesenfranz
Copy link
Contributor

@willyaranda which design do you prefer? Otherwise I'm pretty much ready for a PR ☀️

@willyaranda
Copy link
Member

No timer :)

@Timmaks
Copy link
Contributor

Timmaks commented Dec 30, 2014

I would suggest no timer and hide the blue Progressbar as soon the button is active.

@willyaranda
Copy link
Member

@duesenfranz
Copy link
Contributor

@willyaranda wow nice ☀️

Altough note that new tokenData is older that the one we had ;)

@willyaranda
Copy link
Member

True! I don't know if that's a problem… or not… Could you make a PR to get the old (new, actually) values back? I can only merge from here.

@duesenfranz
Copy link
Contributor

I don't think it's that important, I'll send a PR when I have time ☀️

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants