please stop changing the API , 4 times in a year

Unity Services
1

This is not serious…

I have just ported to the new one and there is a warning that will be deprecated

2

Hello Camtrack,

I just checked if 1.04 package changes affected on my implementation , but there is no problem and I used 1.03 package in my app. I think its backward compatible some how.

Thanks,

3

applifier api v1 → applifier api v2 → unity ads (now doc tells will be deprectaed) → advertisment api

this in less than 12 moths

4

Ohh you were using Applifier…

Actually this a serious integration of Applifier with Unity.
I mean if I didnt use Unity I even dont know there is a add network named applifier.
With this integration this ad network becomes more reliable.

Regards,

5

Hi Camtrack,

I understand this might be irritating to you. We of course aim to be as much backward compatible as possible.

The old applifier native API’s have been and still are backward compatible, so you could update them without changing any methods or the way how you call them. These API’s are meant to be used when you are doing non-Unity development (Objective-C and Java).

The old Unity Plugin (that you probably have used) had problems that sometimes caused problems in build phase. This is probably what you are referring as being deprecated. The package you can download from Asset Store is not going to be deprecated. We suggest that you use the Asset store package.

The reason why we decided to change the API from our old Applifier Unity plugin to the current Unity Ads API, is that we realised that the API was a bit too error prone (it was IMO too easy to integrate the SDK in a wrong way) and not all the methods were properly named (or even misleading in places)

The current API is IMO reasonably simple and provides all the same functionality as the old-one.

Also I don’t see any needs for our current API to be changed. We will of course work on making the client better, but no API changes.

Cheers,
Heikki

2 Likes