IMMANUEL INFANT RAJ is a iOS Engineer has 4.8 YEARS of IT Industry experience and 4.8 Years of relevant experience. His current location is Chennai, India and he is willing to relocate anywhere across globe. His area of Expertise are IOS, OBJECTIVE-C, SWIFT, TvOS, WatchOS. He out for work sponsorship. He is available within 60 Days. If interested please E-mail him at SIMMANUEL88@GMAIL.COM or contact him at +91-999.400.8424.
LinkedIn Profile: https://in.linkedin.com/in/immanuel-infant-raj-92812a52
via An Introduction to Swift from a Python Perspective | Netsight.
Back in 2014 Apple introduced a new programming language called Swift, marketing it as a “powerful and intuitive programming language for iOS, OS X, and watchOS”. The obvious strengths over Objective-C (which is around 20 years old) being improved code readability and a reduced learning curve. I recently spent two days with Richard from Amsys – an Apple Authorised Training Centre – learning some more about the second release of this new language, Swift 2, which will be formally released in autumn 2015.
My coding background is in Python, a language which historically is quite easy to get into, has very readable code, and is highly extendible. At Netsight we have a truckload of experience with Python, as well as experience with Objective-C (iPhone apps, OS X tools). After seeing Apple’s original keynote on Swift, I was keen to learn what it could mean for us as an Internet solutions company.
Having myself developed a few apps in Objective-C in the past I was pleasantly surprised to find that Swift was quite clearly an improvement for my use case, and a lot more fun to get your teeth into. It clearly borrows quite a few concepts from Python (and other languages such as Haskell) so no surprise that it didn’t take me long to get stuck in.
Here I try to provide a summary of some of the main differences I noted coming from a Python background, for the benefit of my colleagues and anyone else who is interested.
A quick disclaimer: I’m new to Swift so I’m sure there will be a host of alternate ways to achieve similar results. Feedback is very welcome!
via Getting data to your WatchKit app.
Update Aug 27, 2015: I’ve written an updated post for WatchOS 2+. This article will still work with WatchKit based apps running on WatchOS 2, but if you’re planning on writing a native WatchOS app check the new article out.
With WatchKit beta 2 Apple provided an easy new way for developers to ask their iPhone app (what Apple is calling the “parent” app) for data:
WKInterfaceController. That works great for many situations, but Apple has also recommended the use of the C-levelDawrin notification center for communication.
Add these on top of the existing use of
NSUserDefaults initWithSuite: that was introduced for extension communication and we’re got a lot of ways to communicate.
via Getting Data to Your WatchOS 2 App.
Previously I wrote about the various methods I was leveraging in WatchKit to communicate between my iPhone app and my watch app.
With WatchOS 2 all that is out the window. We can now write native apps that run right on the watch.
You can still write a WatchKit based app where the watch app’s code executes on the phone and just pushes UI changes to the watch, but I see little future going down that path. Instead I’d recommend writing a WatchOS-based app where all the code actually executes on the watch. This should dramatically speed up the responsiveness of your apps, and the changes to get there aren’t too painful.
Going this route means your data has to be kept in sync using bluetooth. You can’t rely on shared app group containers, CFNotificationCenter, or shared CoreData stores.
via How to Create an Apple Watch App using WatchKit.
In this post I’m going to show you how to create a Hello World app for the Apple Watch using the WatchKit. As you know, WatchKit is Apple’s new development framework, released on November 18th, 2014 along with the Xcode 6.2 beta. This powerful SDK let’s you create and develop apps for the Apple Watch.
via First steps with Android Wear.
Announced during Google I/O 2014, Android Wear is the Android platform for wearable devices. It extends the Android platform to a new generation of devices with a user experience targeting wearables’ specifities. Actually only Smart Watches are supported by Android Wear but trust that Google will extend the platform into other forms of wearables in the near future.
Actually, Android Wear have several use cases :
- Measure fitness activities
- Get notifications of new mails, calls and text messages
- Reponse to texts, emails and instant messages by voice
- Control various stuffs of your Android Smartphone from your Smart Watch like Play / Pause music for example
- Ask questions and get answers thanks to Google Now simply by saying “Ok Google”
via Interactive watch faces with the latest Android Wear update | Android Developers Blog.
The Android Wear team is rolling out a new update that includes support for interactive watch faces. Now, you can detect taps on the watch face to provide information quickly, without having to open an app. This gives you new opportunities to make your watch face more engaging and interesting. For example, in this animation for the Pujie Black watch face, you can see that just touching the calendar indicator quickly changes the watch face to show the agenda for the day, making the watch face more helpful and engaging.