Mahngiel Posted June 12, 2012 Share Posted June 12, 2012 Something I've been juggling a while is the consideration for API keys when building a project for a client which will be out of your management once the project is complete. Registering for API keys normally takes a developer account, signing User Agreements, and some detailed registration info that pertains to the domain the scripts will be operating from. So, what do you do? Make them sign up for everything (can be a difficult process)? Sign up under your dev account and leave it? Write it under yours and after it works sign them up under their accounts and transfer? Or... ? Quote Link to comment Share on other sites More sharing options...
requinix Posted June 12, 2012 Share Posted June 12, 2012 You agree to it for your own keys, they agree to it for their own keys. The two sets are completely separate. Don't give them your keys, but if they chose to give you theirs then that's their choice. Quote Link to comment Share on other sites More sharing options...
Mahngiel Posted June 12, 2012 Author Share Posted June 12, 2012 So then for the QA processes, you're utilizing your own accounts. When it comes to the handover you give them a listing of all the places they need accounts for and how to get the keys, then where to put them. For example, they'd need to go set up their Company FB Page, Twitter, and Google Acct, then apply for dev keys for them all. I mean, it's completely understandable, just seems like it could be difficult for somebody who hired a dev in the first place. Quote Link to comment Share on other sites More sharing options...
requinix Posted June 12, 2012 Share Posted June 12, 2012 You can QA on your end to make sure you got things right, but then you can QA with them to make sure everything is set up right on their end. Maybe there are account settings that need to change, or options to enable, or stuff like that. And yes, you may need to help them do it, but make sure that ultimately they are the ones agreeing to the terms and conditions and whatnot. Developer accounts tend to have different agreements than production accounts: you'd probably use the former while they'd use the latter. If they're not so familiar with this then you can hold their hand through it. Sit down with them as they sign up for the keys and explain to them the things that they might not understand. Once that's done you can use their keys to do the final testing, after which it should all be ready to go. (Or maybe this all happens earlier on and you use the keys when you're comfortable enough to switch from yours.) Quote Link to comment Share on other sites More sharing options...
Mahngiel Posted June 12, 2012 Author Share Posted June 12, 2012 Cheers for you insight, requinix. Maybe it'll be a good thing to populate some PDFs with images for how to sign up for the various sites and keep on hand for when a client needs a walk-through. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.