Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
A developer's take on Watch SDK
- Thread starter Rogifan
- Start date
- Sort by reaction score
That was a demo of a concept extension that was to be made by Tinrocket. It looks like Tinrocket failed to deliver the extension.
While we can't be 100% sure that Nike Facebook Tweeter or American Airlines are capable of following through on the Apps shown, I'd put a lot more faith in them over a small compony.
Do you doubt that Nike Facebook Tweeter or American Airlines will offer aWatch Apps?
I don't doubt it but I have a doubt about whether it'll be the same as the one Apple showed.
You don't know what you're doing.
Hmm. While I love to take suggestions in direction, I can't help but call out blatantly false information when I see it. Everything you have said about WatchKit being even remotely close to a drop in replacement for UIKIt is wrong. These apps function more like Today widgets than iOS apps. I'd be happy show you, but I doubt you care.
@Julien
No one knows for sure. Local apps and Extension apps both present themselves to the WatchOS home screen the same way. Apple allows outside developers access to developing SDK components, so there is a chance they do -but we probably won't see them on the Watch until local apps are released into the wild.
Yeah, yeah, right... whatever... then develop those watch apps... oh never mind if you don't have an idea...
This is a consumers site... of course what you say is BS, but doesn't matter, what matters to users is that the things works.
If you know, then show me
I'm always ready to learn.
It simple: learn about computer science (a degree in one of the few good universities is a good way), then get some experience in apple's sdk's, then read watch kit documentation.
When programming for iOS, you link UI a elements to class variables and methods in a controller class.
To make that work for the apple watch UI a, you have to design the watch UI, and link those elements to the same class variables and methods on the controller class...
No real specifics were shown about the way the Nike+ App would work on the aWatch. However on the Tweeter App it was said you could respond or compose a Tweet from the aWatch. This would mean mic access and Siri dictation. Do Actionable Notifications allow mic access and all actions involved in Tweeting?
If this is the case it may be the Nike+ App is just (more or less) a notification for the iPhone App. I hope we can have at least a couple of fitness aWatch Apps instead of just having to use the OEM.
Last edited:
Absolutely wrong and not possible with WatchKit. You know nothing about it, and are showing your ignorance by trying to explain.
All I needed to see was your knowledge level, to make sure I wasn't avoiding some real advice, and from that snippet there, I know that you know little to nothing about this... #
You are waisting your time. Tanegashima will have the last word no matter how obtuse it is. If you want an idea of what you are dealing with just look at the "Do you really need your iPhone all the time?" thread starting with post 19.
Too funny and it only gets more bizarre.
Then how it is?
Why it is not possible.
That's right, you don't know, because you're just another guy who doesn't understand anything about iOS programming, so full of hate.
You seem to be really upset and take it personally when someone tells you that you're wrong. It's nothing against you, even though I don't care for you attitude, just that you're incorrect.
I saw from another thread that you were just beginning iOS programming. I would think that someone who was just beginning would be apt to someone providing accurate advice and has a history in iOS, while actively working in Watch App dev.
But here:
One reason it is not possible: Imagine you have a UITableViewController in your iOS app that you've used to create a nice table list. You've populate it with a few items using numberOfSectionsInTableView:, tableView:numberOfRowsInSection:, and tableView:cellForRowAtIndexPath:. Simple, elegant, standard regardless of if you've separated the dataSource from your controller.
First off, WatchKit does not support UITableViewController, nor does it's equivalent support those methods. In fact, not even UIViewController is supported. Instead you rely on WKInterfaceController for the heavily lifting (which doesn't support things like viewDidLoad:, viewDidAppear:, etc but instead uses a single willActivate: method). WKInterfaceTable is UITableViewController's equal. Perhaps you should take at this NSHipstser article, it'll steer you in the right direction if you want to get into that segment.
Another reason is that these extensions aren't actually your apps, and don't necessarily run in the same playground. I would love to go into detail, but that's a pretty vast subject. Instead, you should refer to Apple's extensions, specifically taking a look at Today extensions. But of course, nothing will be more clear than taking a look at Apple's actual Watch App exentions guide
Last edited:
I already said about that.
Of course the WK UI elements aren't orthogonal, but you can use the same Controller and Model.
Oh really?
So how?
Since controllers are the least reusable pieces of code, I'd love for you to share this first hand experience of how you link a elements and cram them into these mystical huge controllers that can function universally, in and out of extensions, across platforms where components (UIKit) aren't supported. Please, enlighten me how you "reuse" controllers (not model, in most cases, which is much different) when they have no conformity without any complexity, without loss of efficiency, and how it is better than how Apple themselves suggest you construct extensions.
Until you show me this with code, I have no other reason by to write you off as a beginner who talks big about ideas with big words without any sort of experience or even ideal of implementation. But if not, I'd really like to learn more efficient ways.
Last edited:
I really enjoy reading David Smith's blog. His latest post talks about designing a podcast app and he shows examples of different design stages until he got to an almost finished design.
http://david-smith.org
http://david-smith.org
I really enjoy reading David Smith's blog. His latest post talks about designing a podcast app and he shows examples of different design stages until he got to an almost finished design.
http://david-smith.org
He sure made it look simple...
It's funny and sad at the same time, that the current situation with smartwatches puts Apple in Android's position circa 2010-ish making kludgy moves, while Samsung and other smartwatch makers are in Apple's chair making awesome products. (such as Gear S)has a lot of catch-up to do, like Android had several years ago. After reading Watch documentation, it feels like a handicap joke. "Apple Watch must be paired with the users iPhone for your app to run." You gotta be kidding,
Your product bias to justify your purchase is laughable.