Click to Call button using an Android phone?

mrtrance · 24th Jun 2012, 01:16 PM

So I have a Samsung Vibrant Android phone that I use to test the mobile sites that I work on. One thing that I noticed is when I press the "Click to Call" button on a mobile site my phone will first display the number I want to call and then I have to press a 2nd time to actually make the call. I'm thinking this is just the way my phone is setup and has nothing to do with mobile site coding.

So is this the same way with all Android devices or is it just this particular phone model that I have? I know even when I'm trying to make a call from my contact's list when I select a contact it will again list the name and phone# and I have to press the "Call" button again to actually make the call.

What I'd like to see is if I could make it so that when someone presses the "Click to Call" it will automatically dial out in just one click instead of 2 clicks. Is that even possible or will that work with other devices and it's just not the way it works with my phone?

Any feedback?

App29 · 24th Jun 2012, 01:55 PM

Originally Posted by mrtrance

So I have a Samsung Vibrant Android phone that I use to test the mobile sites that I work on. One thing that I noticed is when I press the "Click to Call" button on a mobile site my phone will first display the number I want to call and then I have to press a 2nd time to actually make the call. I'm thinking this is just the way my phone is setup and has nothing to do with mobile site coding.

So is this the same way with all Android devices or is it just this particular phone model that I have? I know even when I'm trying to make a call from my contact's list when I select a contact it will again list the name and phone# and I have to press the "Call" button again to actually make the call.

What I'd like to see is if I could make it so that when someone presses the "Click to Call" it will automatically dial out in just one click instead of 2 clicks. Is that even possible or will that work with other devices and it's just not the way it works with my phone?

Any feedback?

This an issue with the code not your phone. On the apps I do it offers one touch. Why aren't you pushing apps? Just curious.

Jay Moreno · 24th Jun 2012, 04:30 PM

Originally Posted by mrtrance

So I have a Samsung Vibrant Android phone that I use to test the mobile sites that I work on. One thing that I noticed is when I press the "Click to Call" button on a mobile site my phone will first display the number I want to call and then I have to press a 2nd time to actually make the call. I'm thinking this is just the way my phone is setup and has nothing to do with mobile site coding.

So is this the same way with all Android devices or is it just this particular phone model that I have? I know even when I'm trying to make a call from my contact's list when I select a contact it will again list the name and phone# and I have to press the "Call" button again to actually make the call.

What I'd like to see is if I could make it so that when someone presses the "Click to Call" it will automatically dial out in just one click instead of 2 clicks. Is that even possible or will that work with other devices and it's just not the way it works with my phone?

Any feedback?

From a mobile website that is how it happens on all phones that i am aware of - if it didn't rogue developers could set scripts up to auto-call premium numbers... it maybe different for apps but kinda makes sense.

I recall in Apple Dev notes similar features where added to prevent SMS messages not being pre-populated and also have video/audio not auto start...

I guess its down to them making it ask for user permission... if it didn't you could inadvertently click any button and have it call a rogue premium number am surprised APP29 that your apps are allowed to do that.

bizadpros · 24th Jun 2012, 08:03 PM

Originally Posted by Jay Moreno

From a mobile website that is how it happens on all phones that i am aware of - if it didn't rogue developers could set scripts up to auto-call premium numbers... it maybe different for apps but kinda makes sense.

I recall in Apple Dev notes similar features where added to prevent SMS messages not being pre-populated and also have video/audio not auto start...

I guess its down to them making it ask for user permission... if it didn't you could inadvertently click any button and have it call a rogue premium number am surprised APP29 that your apps are allowed to do that.

Agree with Jay, most sites with a click to call simply open up the number in the dial-pad. If using an app, you probably do indeed need to have permissions set up - as in apps.

App29 · 24th Jun 2012, 09:18 PM

Apple requires full disclosure. You must identify the element's clear intentions..."Click to call, Call, etc. We focus on userability and convenience. If the user clicks on a button that says Click to call, than why should we interfere with their intention...

Jay Moreno · 25th Jun 2012, 08:24 AM

Originally Posted by App29

Apple requires full disclosure. You must identify the element's clear intentions..."Click to call, Call, etc. We focus on userability and convenience. If the user clicks on a button that says Click to call, than why should we interfere with their intention...

It was my understanding its part of their API and NOT something you can choose to circumnavigate as a developer... if a user clicks on anything that initiates a call surely they have to be prompted to see the number first before it dials? i know i would be pissed if i clicked it and it had me auto-calling a premium $1/second telephone number without letting me know before hand...

Am not saying you would do that but without that extra step to see the number you are calling that would leave Apple/Droid apps completely open to abuse by rogue developers building apps for kids... if you are implementing then thats a cool feature as long as its being used legitimately

App29 · 25th Jun 2012, 11:26 AM

Originally Posted by Jay Moreno

It was my understanding its part of their API and NOT something you can choose to circumnavigate as a developer... if a user clicks on anything that initiates a call surely they have to be prompted to see the number first before it dials? i know i would be pissed if i clicked it and it had me auto-calling a premium $1/second telephone number without letting me know before hand...

Am not saying you would do that but without that extra step to see the number you are calling that would leave Apple/Droid apps completely open to abuse by rogue developers building apps for kids... if you are implementing then thats a cool feature as long as its being used legitimately

What API? Are you referring to the SDK? I was confused by your API comment. Apple goes through a testing of each app submitted, which is why it takes the amount of time it takes to get approved. Consumers must rely on the "good" intentions of the developer, as Apple doesn't always catch the little things. Our customers prefer to have the flow the way we have set it up. However, there's a really cool feature that comes with every mobile phone if the customer deceides after pushing the "Click to Call" button...it's called "End" or "End Call" Just teasing

Jay Moreno · 25th Jun 2012, 04:21 PM

Originally Posted by App29

What API? Are you referring to the SDK? I was confused by your API comment. Apple goes through a testing of each app submitted, which is why it takes the amount of time it takes to get approved. Consumers must rely on the "good" intentions of the developer, as Apple doesn't always catch the little things. Our customers prefer to have the flow the way we have set it up. However, there's a really cool feature that comes with every mobile phone if the customer deceides after pushing the "Click to Call" button...it's called "End" or "End Call" Just teasing

LOL at the end of call feature!

yeah the SDK - am not an app developer just web apps so refer to stuff like that as an API

i got the the apple developer license so as i can use the iphone emulator, but i had to read up on some of the documentation thats what i was referring too as i was trying to find out how to get around the auto-population of sms messages... is that possible with an iphone app? ie pre-populate the body text of an sms message and not just the telephone number its going to get sent to?

@EvanDni ????

Quentin · 25th Jun 2012, 08:58 PM

I am pretty sure that will happen on all phones and also it will depend on each persons preferences which you cannot over ride

Q

WillR · 22nd Jul 2012, 08:56 PM

This is most definitely the way it works on all phones. There would be too much room for mis-use and abuse if things worked the way you are suggesting. You will always need to confirm the call before it is initiated and I think that is a good thing.

John Ayling · 22nd Jul 2012, 09:21 PM

What WillR is saying is exactly right in terms of keeping phones secure from possibly malicious web code.

It's the same sort of thing on a desktop, where a web browser has a 'security sandbox' to stop web code from interacting with the operating system unless the user explicitly allows it.

24th Jun 2012, 01:16 PM	#1
mrtrance Advanced Warrior Join Date: 2008 Posts: 945 Thanks: 4 Thanked 24 Times in 24 Posts	Click to Call button using an Android phone? Share on: So I have a Samsung Vibrant Android phone that I use to test the mobile sites that I work on. One thing that I noticed is when I press the "Click to Call" button on a mobile site my phone will first display the number I want to call and then I have to press a 2nd time to actually make the call. I'm thinking this is just the way my phone is setup and has nothing to do with mobile site coding. So is this the same way with all Android devices or is it just this particular phone model that I have? I know even when I'm trying to make a call from my contact's list when I select a contact it will again list the name and phone# and I have to press the "Call" button again to actually make the call. What I'd like to see is if I could make it so that when someone presses the "Click to Call" it will automatically dial out in just one click instead of 2 clicks. Is that even possible or will that work with other devices and it's just not the way it works with my phone? Any feedback?

24th Jun 2012, 09:18 PM	#5
App29 App Master Join Date: 2012 Location: Sacramento, CA Posts: 68 Thanks: 1 Thanked 3 Times in 3 Posts	Re: Click to Call button using an Android phone? Share on: Apple requires full disclosure. You must identify the element's clear intentions..."Click to call, Call, etc. We focus on userability and convenience. If the user clicks on a button that says Click to call, than why should we interfere with their intention...

25th Jun 2012, 08:58 PM	#9
Quentin Web Marketing For Profit War Room Member Join Date: 2002 Location: Brisbane Posts: 2,895 Thanks: 8 Thanked 1,162 Times in 528 Posts Blog Entries: 10	Re: Click to Call button using an Android phone? Share on: I am pretty sure that will happen on all phones and also it will depend on each persons preferences which you cannot over ride Q
	DIY Product Creation Online Business Training on How To Create Products to sell online Plus Lots More.

22nd Jul 2012, 08:56 PM	#10
WillR Digital Marketer War Room Member Join Date: 2010 Location: Australia Posts: 12,475 Thanks: 1,984 Thanked 8,187 Times in 4,079 Posts	Re: Click to Call button using an Android phone? Share on: This is most definitely the way it works on all phones. There would be too much room for mis-use and abuse if things worked the way you are suggesting. You will always need to confirm the call before it is initiated and I think that is a good thing.
	. ➨ Here's How to Make Your First $177 Online This Week Using the Piggyback Method... .

22nd Jul 2012, 09:21 PM	#11
John Ayling HyperActive Warrior War Room Member Join Date: 2009 Location: Australia Posts: 225 Thanks: 41 Thanked 47 Times in 36 Posts	Re: Click to Call button using an Android phone? Share on: What WillR is saying is exactly right in terms of keeping phones secure from possibly malicious web code. It's the same sort of thing on a desktop, where a web browser has a 'security sandbox' to stop web code from interacting with the operating system unless the user explicitly allows it.
	Software Marketing & Licensing System for WordPress Plugins, Themes & .NET Software >> 72 Hour Special <<