I would like to get a statistics on how many people are using SDK that I'm providing. What functions they use the most and etc.
For apps I used firebase/fabric in order to track all that. But those services come with a responsibility (privacy policy). And if I just pack them into SDK that may conflict with people apps who don't want any tracking SDK being included in their Apps.
So the question is, are there any services that provides SDK tracking without violating privacy policy of user data collecting?
So far I was not able to find any of those specifically for SDK.
As a side question, If such analytics is taken place in SDK, should it be explicitly written in SDK description?. And should the people who integrate such SDK explicitly write in their app description that particular SDK is collecting their usage?
I have a roadside assistance service application. It has some of the functionalities similar to ride booking app(Eg. Uber). How far can i leverage iOS 10 Sirikit? May be, apple can reject it. But i need to know the technical feasibility.
My application's functionality - I am struck in the middle of road with a flat tire. I need a tow assistance for my car. I give my current location and i ask my app to tow to my preferred dealer location. I pay for the service and wait for the provider to respond. I receive continuous updates from my service provider regarding the driver.
1st Step tried: I am trying to open my app with the statement "Siri, get a roadside assistance for my flat tire". I need to open my app and capture FLAT TIRE as a parameter. But I couldn't.
I tried using AppIntentVocabulary.plist. It was not working. I am missing something and there are no complete tutorials over the internet. Any help is much appreciated.
Sample Project:
Github Link for my simple Siri Integration:
https://github.com/vivinjeganathan/SiriExample
This documentation contains preliminary information about an API or technology in development. This information is subject to change, and software implemented according to this documentation should be tested with final operating system software.
SiriKit is a way for you to make your content available through Siri. It also lets you add support for your services to the Maps app. To support SiriKit, you use the Intents framework and Intents UI framework to implement one or more extensions that you then include inside your iOS app. When the user requests specific types of services through Siri or Maps, the system uses your extensions to provide those services.
Add SiriKit support only if your app implements one of the following types of services:
Audio or video calling
Messaging
Payments
Searching photos
Workouts
Ride booking
Check this Link: http://airflypan.com/foundation-course/233
http://airflypan.com/foundation-course/233
You really can't do this in any sensible way for the user. Although you app's usecase will map to ride-hailing intent the vocabulary will not. Siri gives you almost no options to influence the vocabulary she is using to communicate to your User. If you could only teach you users that requesting a tow is actually requesting a ride... :)
Apple have analyzed the domains they are supporting and the vocabulary that is used in these domains and "taught" them to Siri in every language/culture that Siri is supporting. This makes total sense from Apple's point of view because you'd be hard pressed to be able to do this yourself.
I hope this is not off topic for StackOverflow since it is not just software development related but also marketing. But I guess this problem is something we developers are all confronted to.
To monitor and market our iOS app, we use a bunch of third party SDKs:
Google Analytics to understand what's happening
a push notification system (e.g. Urban Airship)
a "smart" review prompting engine (e.g. Apptentive)
a testing / crash reporting system (e.g. Testflight)
should you want to run app installs ads, you also need the FB SDK, an SDK to track Twitter conversions, etc.
you may also want to track where other installs come from via something like Tapstream.
So we are already running more than 6 3rd party SDKs in our app, and it does not feel right:
each of them will do some kind of hand shake every time the app is opened
it's as many potential issues
each of them will have a different web interface
Is there a way to optimise all this, i.e. to have just one SDK doing most things? Or does someone know of a lib to wrap all this stuff under one lib for instance?
There is no getting around a few of these. If you want to talk with FaceBook, Twitter, etc. You will need their SDK no matter the 3rd party SDK you choose.
You could actually write your own setup to track and deal with everything, but there are those that have done it before.
For example, Parse will do:
Analytics
push notifications
a "smart" review prompting engine (you can do this yourself by reviewing the analytics)
crash reporting system
it also uses FB SDK, Twitter SDK already to help with user logins where users my want to use their credentials from their sites on your app
user login
cloud database
You could technically throw an "event" into the analytics to track how many folks are using your app that was installed from x store. However, this would require a different version of your app for each store. Sounds like an interesting idea none the less. Tapstreme and others are basically marketing though, not really something required to do something specific. You will need an SDK if they are tracking something specific themselves.
one web interface
There are multiple systems built like this. they are called BaaS or Backend as a Service.
Hope this helps, Cheers
In my App, I have used MGTwitter Engine. I used twitter in many files in app.
Now there is Twitter 1.1 is announced.
I want to know where I can download API 1.1 for iOS.
What are changes I need to do in my existing code?
I tried to read the documentation of twitter, but new version looks much different than previous which I am using.
Based on latest fragmentation report - http://appleinsider.com/articles/13/06/20/apple-now-charting-app-store-ios-fragmentation-just-like-googles-android there is no need in implementing Twitter as external library/SDK.
Currently there is more than 93% users on iOS 6 and plus 5% iOS 5. You can safely use internal iOS integration of Twitter and cover 98% users.
Read here about this: http://developer.apple.com/library/ios/#documentation/Twitter/Reference/TwitterFrameworkReference/_index.html
If you will still want to use external library - please se the ShareKit https://github.com/ShareKit/ShareKit I believe that they have already implemented 1.1 API. But since I don't use their library I'm not 100% sure.
I have done routing in iOS apps before, but with iOS6 we are now displaying Apple maps - which causes a problem because we are using Google routing data and if we use Google data, we are supposed to be displaying it on a Google map.
I have been searching but as far as I can tell, Apple does not provide any routing data. The closest thing to an answer so far seems to be when Apple says Apps that consume direction information do so by sending an appropriate request to the Maps app, which then handles the task of displaying that information to the user. - which, to me, means that the Maps app would be opened to display the route, and taking the user out of our app.
Where can we get on-the-fly routing data that is acceptable to use on iOS6 apps using Apple's maps?
You could use MapQuest's Open Directions API. It is free and it does not seem to have any limit. They also have a licensed API with a free daily limit.
I believe you are only required to put their logo somewhere on your app.
Unfortunately MapKit does not provide routing data.
In iOS 6 and later, Map Kit offers support for providing map-based
directions to the user. Apps can be a provider of directions or they
can use the Maps app itself to provide directions. Apps that consume
direction information do so by sending an appropriate request to the
Maps app, which then handles the task of displaying that information
to the user. However, if you are implementing a navigation app of your
own, you can register your app as a routing app—that is, a provider of
directions. When the Maps app receives direction requests from the
user (or other apps), it can then forward those requests to your app
for display.
Source
So, your best bet here is to use external routing data, or the maps app. Since Google prohibits using their routing data without displaying on a Google map, you may want to check the bing API's (here). It is not immediately apparent that they require you to use bing maps with the bing routing data, but they do also provide a static map api as well (here).
Alternately, you may want to look at this project on github. It shows how to load google map tiles in a map view.
Best of luck.
Apple may provide routing information in the future, but for now it's only available in the Maps app.
One solution is to use Google tiles in your map view. The code for ClassicMap has a complete implementation of this, and is available with a liberal license. Use it as a stopgap until Apple provides routing information.
You are correct, the Google API terms of service state in 10.1.1 point g:
(g) No Use of Content without a Google Map. You must not use or display the Content without a corresponding Google map, unless you are
explicitly permitted to do so in the Maps APIs Documentation, or
through written permission from Google. In any event, you must not use
or display the Content on or in conjunction with a non-Google map. For
example, you must not use geocodes obtained through the Service in
conjunction with a non-Google map. As another example, you must not
display Street View imagery alongside a non-Google map, but you may
display Street View imagery without a corresponding Google map because
the Maps APIs Documentation explicitly permits you to do so.
The access to the Google APIs was until iOS 6 transparent and accessed via the MapKit framework by Apple, who handled all the licensing, fees etc for us the developers, we didn't need to worry about this.
Now that Apple are using their own mapping service, we don't have access to Google APIs via the MapKit framework, like you say, and routing isn't possible with MapKit in the way you want to use it.
So you must keep the communication with Google, but the problem is now you will be using Google data without a Google Map.
This is a problem, and if your app's popular, and Google realise, they may choose to make a problem with you.
There isn't a correct way around it for now, some apps are tiling Google maps onto Apple maps, but then you will need to register your app with Google for an API key I assume, which limits your number of requests and potentially you may have to pay Google for the API usage.