API integration, anyone else hate it ?

[aladine]

Hello and merry Christmas everyone !! 

 

Well i was just fighting my way in order to integrate one of the client API and i just fed up and decided to find if anyone share this issue with me, cause it would really sucks if am the only one lol 

 

thank you 

[plicatibu]

My experience integration APIs are just with ads / analçytics for my own projects.

 

But, yes, I dislike to do it too.

[alex_h]

If you think about it all the client APIs are looking out for much the same game events:

• game start
• level complete
• player score
• game end
• etc

I've found the simplest thing to do is make each game dispatch events to a generic client API handler at these points. Then whenever I configure a build for a client with a new API I just have to add their function calls in to the existing generic client API handler, which takes only a few minutes to do. 

Where it potentially gets more complex is when you have to expose methods of your game to calls from the client side like sound on / off, pause / unpause. But then if you get it working once you can just copy that across any future games.

[aladine]

alex_h

i never had a client who asked for such an API they all want Ads , in-game-purchase, leaderboards ands sometimes the ability to integrate Facebook, those are the real pain in the ass xD

[RazorSharpFang]

The APIs that require users to log in are the hardest to implement, sending a http request to /login.php and waiting for the response, checking the response, updating the game, ugh.

 

That aside, the only APIs I have used is the gamejolt api, for their user logins, leader-boards, high-scores, achievements, etc... 

and the clay.io api, for advertisements, leaderboards, and stuff. 

 

Haven't done any games yet that require user payment. I can only imagine the horrors within... : /

 

That said, I've never sold a html5 game before, so I can do whatever I want with it. ( yay )