I want to integrate Skype APIs in my native app. Is that possible? I have Googled around and couldn't find a way to start. I know there are APIs available for Mac OS X.
Can I make use of those APIs for my iPhone app? I know it is possible, as many apps like Nimbuzz have integrated Skype APIs in their iPhone apps.
Skype has a Public API which you can reference. This page has a wealth of information on how to use the API and the various commands. There is no public framework which abstracts it any further so you'll need to investigate how to make the actual commands by deconstructing the various wrappers.
I don't think Skype wants to particularly bring their API wrappers to the iPhone because you'd be competing directly with their own application. They do provide Cocoa wrappers but those are in the form of a framework and you can't have your own custom frameworks in an iPhone Application (only Apple approved ones). Also relevant: Skype bans Nimbuzz and fring while faking stats
SkypeKit sounds like what you want.
SkypeKit prohibits development on iOS devices. What may be of use to you is the URI scheme, This should let you open the skype App on your iPhone and place a call.
For additional help visit the Skype Developer Forum
Related
I've spent the day googling all the leads on developing iphone apps on Windows and apart from buying a mac the most suitable route seems to be Phonegap. I cannot find out whether Phonegap gives access to all the native functionality. For example I want to access and manipulate the address book contents. I also want to be able to send text messages programatically and intercept and examine incoming text messages. It would be helpful if someone could confirm whether this can be done with Phonegap.
My understanding is that Phonegap is based on webapps but I am assuming that an app developed with it can run offline for operations that dont require internet access.
Even using Phonegap you will still need access to a mac to actually build your iOS application. This is a restriction that Apple has in place, and to my knowledge there is no way around it.
Phonegap uses a UIWebView to display your application built using HTML, CSS, Javascript etc, but this does not mean that an Internet connection is required for the app to run (so offline apps are definitely possible).
With regards to Phonegap's functionality, details of the Phonegap API can be found on their website. Specific to your needs, I believe phonegap provides access to the device's address book through the contacts API:
http://docs.phonegap.com/en/2.3.0/cordova_contacts_contacts.md.html#Contacts
I don't think Phonegap provides the ability to send SMS messages itself, but many people have developed extensions to add extra functionality to their applications through plugins. The majority of Phonegap iOS plugins can found at the following GitHub repo. The plugin I think you require is the SMSComposer:
https://github.com/phonegap/phonegap-plugins/tree/master/iOS/SMSComposer
I'm a little bit confused now. There is a weather and stock widget on the iPhone. Is it possible to create such a widget yourself? I don't want to talk about new features in iOS 5 here. I only want to know it in general (iOS < 5).
Here I found the introduction guide with the help of Dashcode.
Wikipedia also states that this is not possible. I always thought it would be.
So are there only web apps and native apps possible?
PS: What is a widget exactly? A combination of native app and HTML, CSS, Javascript? Only HTML, CSS, Javascript? A cocoa application?
No, iOS does not currently allow the creation of widgets. The weather and stock widgets you're talking about were created by Apple. There are no APIs to write your own.
As of iOS8, its possible. 3rd party apps will be able to create widgets for the notification center.
http://www.apple.com/pr/library/2014/06/02Apple-Releases-iOS-8-SDK-With-Over-4-000-New-APIs.html
This isn't a Guide for iOS Widgets, it's Guide for Mac Dashboard Widgets.
You can't
create iOS Widgets
change how the iOS Notifications Appear
With Dashcode you can create Web Applications for both iOS and Mac. It's a combination of HTML, CSS and JavaScript. Those Web Applications are only available on the Web (e.g. Safari). If you wan't to create a native App you have two possibilities:
Create a real native Application in ObjC
Create a Web Application (e.g. with Dashcode) and load it into a UIWebView, this requires also ObjC.
Advantages
Web-only Application (Browser-App)
You don't need a Apple Developer Account
Easy to port to Mac and other Smartphones
Unreal-native Application (Browser-App in a native App)
Easy to port to other Smartphones
It feels like a real native app
Your app is on the App Store
Native Application (Real iOS-App)
You have full access to the iPhone Frameworks (e.g. Contacts.app)
Your app is on the App Store
Disadvantages
Web-only Application (Browser-App)
The user needs to know your URL
You're not in the App Store
Unreal-native Application (Browser-App in a native App)
You need to pay 99$/year for an Apple Developer Account
It could feel like it's not a native app
You have not the full access to the iPhone Frameworks except you use something like PhoneGap or ObjC
Native Application (Real iOS-App)
You need to pay 99$/year for an Apple Developer Account
You can't port your app easy to other Smartphone
You need to learn ObjC
No, currently thats not possible. But you can, and should, file a feature request at bugreport.apple.com so that this issue gets some attention.
There is no reason you can't create a widget like component using javascript and display it in a uiwebview. This works equally well in android and iOS
A few years ago when I was involved with java server pages development I put together a tutorial of using dashcode to wrap java or javascript components.
http://www.jsfcentral.com/listings/A21034;jsessionid=A15086803ABF96A63DB1AB5405C9A329?link
I'm about to begin development of an iPhone app. The app itself is fairly basic, and I want a speedy turnaround time.
I'm a web developer myself, specialising in traditional web technologies such as PHP/MySQL; I have no experience in Objective-C.
My plan was to create a very basic iPhone app that is just a Safari service that passes some basic variables to a URL. That URL is the app built in PHP and housed on my servers, this way I can create the app very quickly without needing to outsource anything.
My question is whether apps of this nature would be accepted into the iTunes store, or would they be out-right rejected? Anyone's experiences or comments are very welcome.
Thanks
It could go either way, but mind bullet 12.3 from the App Store Review Guidelines:
12.3 Apps that are simply web clippings, content aggregators, or a collection of links, may be rejected
In my opinion, a simple UIWebView wrapper around your web site comes close to the definition of a simple web clipping. Your approval may very well hinge on your luck in drawing a sympathetic reviewer.
It really depends upon your application...These kinds of application have been approved in the past but again I am saying that it depends on many factors.
Try to test your app in every possible manner and also keep in mind the memory issues.
Best of luck!!!
Should be fine - its called a web app and there is software out there that will do just this for you.
All you need to do is to make a UIWebView and put your web app into it.
Also look at http://jqtouch.com. That gives you some idea of what you can do web-side. :)
http://www.netbiscuits.com/559
Native Hybrid Apps
Native apps can interface more deeply
with the mobile handset modules and
sensors to create an even richer
mobile user experience. Netbiscuits
provides pre-build native apps
frameworks for all major mobile
operating systems to be easily
customized for the needs of
enterprises.
Get "2in1" by combining the power of
mobile websites and native apps by
wrapping mobile websites into hybrid
apps and list them easily in all major
app stores of providers like Apple,
Nokia, Google or Samsung to open a new
mobile distribution channel. The
benefits of this approach are fast
time to market, minimized development
and maintenance efforts and maximum
mobile cross-platform technology
coverage.
Yes, it will be accepted as long as you stick with HTML, CSS, JS and Obj-C on the client side. You still need to wrap it in an iPhone app. In my experience, the best way to this is to use http://www.phonegap.com/ or a similar framework.
You'll have the option of deploying you app through iTunes or as a regular web app (you users will be able to create a link to your web app right on their springboards)
It SHOULD be accepted, granted you test test test and make it look just like a native application. Also you'll have to make sure that your server is never down, or if the application can't reach it just display an error message. You also have to keep in mind that there are a lot of iPod Touch users, and they don't have access to the internet all the time. Which means that chances are you'll get a BUNCH of 1 star reviews
I'm working on an interface for an existing web application that will allow iPhone and other mobile clients.
I have started implement a JSON API and I need to give some detailed specificaitions for the App to an iPhone developer.
What I am curious about is whether other developers are using session data in their JSON / mobile client communications.
Do the common url grabbing libraries of iPhones (and other mobile devices) mimic a browser's cookie handling?
Can someone suggest what libraries might be used to achieve this? Are there any online tutorials or blog entries that outline state based web connectivity in an iPhone app?
I've used ASIHTTP (http://allseeing-i.com/ASIHTTPRequest/) and JSONFramework (http://code.google.com/p/json-framework/) to achieve this.
Both very good libraries that are easy to work with.
I think about starting from scratch building a small application fullfilling two technical requirements:
should be usable on iPhone
should work offline
There are two obvious alternatives here to choose between
A real iPhone application with offline capabilities
A web app using HTML5 offline, Google Gears or similar
Having no iPhone app development experience (I don't own an iPhone), i wonder which way would be the easiest to go?
What are the learning curves for building offline HTML vs building an iPhone app?
Honestly, it depends what your app is going to do.
MobileSafari supports all the HTML5 offline stuff, so you could store data in a clientside SQL database, cache the application clientside, etc... The mobile Gmail app is probably the most notable example of that, giving you full-featured access to your Gmail even when offline. You can also use geolocation through JavaScript APIs that were added in 3.0. Web Clips let your web app share the home screen with native applications too. There is more on using web apps on the iPhone on this Stack Overflow post.
Obviously, doing a Web app will be of interest to people who like dealing with HTML, CSS, and JavaScript (and possibly whatever language is running server-side). It is possible to do really neat stuff with offline Web apps, but its performance won't be as good as that of native apps, especially on pre-3GS devices.
Developing a native application will require you to learn Objective-C (or C# as soon as Mono Touch is available to the masses) and pay a $99 fee to be allowed to test on-device and deploy to App Store. A lot more of the system is exposed to you through the various APIs, such as the camera, compass, multitouch, and so on.
Objective-C is pretty simple to pick up if you're familiar with Java; you only really need to get used to the square bracket syntax and memory management and then it's pretty straight-forward.
Then there are the hybrid systems, like PhoneGap, which expose more of the device's APIs, provided the Web app runs in a special container app. It is also crossplatform, so you could also deploy the app on Android and BlackBerry if you wanted to. This still requires you to pay the App Store fee, but if you're more familiar with Web development, this gives you the best of both worlds.
I can't tell you too much about HTML apps in general, but I can tell you that the API for the UIWebView is extremely minimal, and of course there is much less you can do than in a native iPhone application.
An HTML5 offline app would have security issues as you would have to hard code your oauth secret into code that anyone could see ( by clicking view source, or inspecting in Firebug ). You could simply use http auth, but then you get the ugly "from API" credit with every tweet sent from your app, and also that ugly http auth popup from the browser.