Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.
Talk:Enabling wallet payment by face recognition
Nemoryoliver - FANTASTIC WORKjust a FANTASTIC job you have done bro! Many devs will benefit from your work.
13:26, 11 December 2012 (EET)
R2d2rigo - Additional securityYou should write about additional security features (maybe a PIN?) for this method; face recognition is easily hackable if the attacker has a photo of your face obtained via social networks or other methods.
14:22, 11 December 2012 (EET)
Galazzo - Additional security
yes I agree with you as my intention was not to show a method to substitute existent security methods, but as further method. I will cover this point as soon as possible.
About the ease to hack face I'm not so sure is so easy. Mainly depends on your implementation, how strict the threshold is and of course you don't allow to process photo from the device library but just from the camera.
In a real life scenario someone has stolen your phone he/she should also came back home, to break the secure code, to search and find a very good photo of you around the web, print a copy put in front of camera a hope to pass recognition.
I hope in the meanwhile you blocked your phone.The idea is that using PIN secure code, face recognition should be more difficult to stole your data.
15:03, 11 December 2012 (EET)
Aady - I like it ...nice article :)
19:46, 11 December 2012 (EET)
Vaishali Rawat - Thanks for the articleUseful one...
11:38, 12 December 2012 (EET)
Hamishwillee - Subedit/review
Nice use of face recognition - this is an appropriate companion to your other article, and a very cool and innovative approach. You probably do need to add a disclaimer about the recognition effectiveness as a security mechanism (as alluded to by R2d2rigo)
- For me there is not enough code explanation.
For example, you have section "Remapping URI", with text "Into App.xaml.cs add the following code:". I don't like "copy-paste" instructions - answer questions like "Will the URI always contain "PaymentInstrument" - what will it look like. The second block of code where you add the URIMapper into the app could just have an in-code comment.
In another section you say "The following code is needed to register our application into the wallet in order to be able to call it from the Wallet.". It is better to explain briefly how the code works unless it is completely obvious - here you could explain you need to first create the payment thingy, and then add it using a AddWalletItemTask.
Wallet.xaml section explains that it is opened, but not what it does.
Some sections are better than others, but its worth considering all of them.
- Please provide links to other good articles (in devcenter and elsewhere) on using the wallet.
In terms of improvement, it might be worth also showing what the wallet app looks like after payment is approved. If you have no such UI, then you should say so. I'd also have your images of the approval process at the bottom of the introduction (on theory that "a picture tells a thousand words")
You have made a warning that it is hard to get two of the capabilities. I suspect that it is actually "near impossible" to get anywhere near the secure element unless you're a bank - you might want a stronger warning there.
This is an awesome and innovative concept and implementation. I just think it can be improved by providing a little more guidance about how the pieces fit together, what they do, and what is "essential to a wallet app" vs. "this is my implementation of a wallet app".
HOpe that helps and that you are not discouraged. Even as it is this is very cool and most developers could work out what they needed from it.
07:07, 13 December 2012 (EET)
Galazzo - Article improvements
thanks alot for your suggestions that are always welcomed. I started to update my article trying to cove unclear sections.
Also I wish suggestions from other developers about unclear section and future features they would need.
01:21, 14 December 2012 (EET)
SB Dev -I added the required capabilities to the article MetaData as well.
talk) 11:14, 13 September 2013 (EEST)(
Hamishwillee - Thanks Oliver
I saw you broke the link to the DSP project. Does the zip also contain this project (ie have any dependencies). If not, then we need to have a link to that code. I understand DSP.zip will be added soon to the wiki.
talk) 10:39, 16 September 2013 (EEST)(
SB Dev -The link removal was done by the editor before me. I can look into it though.
talk) 11:34, 16 September 2013 (EEST)(
Hamishwillee - No need thanks
I've asked the previous editor "Chintandave er" to clarify.
talk) 04:03, 17 September 2013 (EEST)(
Mukhtaromar - Image Saving to Database
Great article, Can you guide something about how to take picture from windows phone and save it into a database (in sql server) once.... and then retrieve that image and compare with that one.The sql server database must be on a Hosting website or Cloud (not local)
talk) 23:50, 29 November 2013 (EET)(
this is a good solution when your image set is very huge, but then may be worth to move all the recognition process to clod. The on device solution is intented for a reasonable set of images.
talk) 10:47, 1 December 2013 (EET)(
Taps - Missing Method on DSP class
i am getting an error on the below line. DSP.Utilities.ColorToGray(color)the ColorToGray doesnt exist in the class am i missing something?
talk) 16:15, 19 February 2014 (EET)(