qzervaas

In iOS 9 there is SFSafariViewController which doesn't give such control.

Some providers (e.g. Fitbit) require you use this instead of UIWebView in order to access their API, presumably to avoid accessing the DOM.

Not sure exactly how they are enforcing this though, since they don't provide their own OAuth library.

Things I learned: ICQ still exists.

Because fines provide revenue?

I would assume this is to create greater logistical efficiencies in ways we don't see.

Side note, I'd be quite interested to see the details of their contracts with courier companies (e.g. TNT deliver all of their new products here in Australia, although AusPost send/receive product replacements)

The post is almost entirely true for non-games too. I have a successful app and these are the exact things Apple want.

Also, like he said, don't complain, just deal with it. Saying they do nothing for you isn't entirely true, or you wouldn't have an app on the App Store.

You can download the newest Xcode et al without the App Store, from here:

https://developer.apple.com/downloads/

(Edit: You can download Xcode all the way back to Xcode 2.3 from 2006)

I have the Skarsta (the smaller top). It's pretty good, my only two issues with it are:

1) The top is affixed to the leg brackets using plastic screws, and the top tends to move around a little bit. Definitely wouldn't want to pick up / move the desk by holding onto the top only

2) The top was bowed slightly in the middle on the one I bought. My Apple Keyboard would wobble slightly, so I put masking tape on one of the rubber feet.

Try Jaycar instead!

Also, for those interested, RadioShack was called Tandy Electronics in Australia.

If you're on iOS, my understanding is Pebble will write to the Health app.

From there you can analyze the data. You can't export directly using the app, but you can view all records or find one of many apps that support HealthKit which may possibly export for you.

Especially when the current solution offers no upside (slower speed, no cheaper, a rollout that will take just as long).

I like to play "stupid or liar" when it comes to things like this, but I can't figure out which it is when it comes to the NBN decision making.

This is a propaganda piece from NBNco (the company installing Australia's new broadband network). It basically says Internet that is too fast is bad:

http://www.nbnco.com.au/blog/singapores-gigabit-dream-arrive...

Or to put it another way: our bad solution is superior because it's slower.

Not to say your point isn't true, but that has nothing to do with successive governments shitting on each other's plans when it comes to installing infrastructure to houses (or choosing the right infrastructure to install).

My office is "in the city" in Adelaide, a city of 1.25m. Our only reasonably priced option is 12Mbit ADSL2 (which is about 0.8mbps up).

We can get 100mbit fibre for $1000/mo, plus cost of installing the fibre.

We can get 12/12 DSL for $300/mo.

As an app developer, I am often unable to upload anything to iTunes Connect without saturating the link and it timing out. The only feasible option is paying a premium for 4G/LTE speeds on Telstra.

Many (most) of Australians don't even have the option of 10 mbit.

When the new NBN is rolled out, most will have the option for 25 Mbps. This plan is due to be completed by 2020.

Thanks!

Thanks! It's a spinoff from my iPhone app, Streaks (http://streaksapp.com)

Apple's already shown they don't like this behaviour with their randomised MAC addresses in iOS 8+. Obviously what this article references is done at the carrier level, not on open wifi networks.

I expect them to do something about this carrier-level behaviour next iOS. From a technical perspective, what could they do to prevent this?

Half-baked semi-serious idea: An iOS content blocker that prevents scroll-jacking.

Definitely ready. I've had a Swift app out for 4 months and it's been quite successful[1], with no Swift-related issues.

I've just updated the app to Swift 2 and it's all working great.

The only issue has been related to the new Bitcode feature in iOS, which isn't Swift-specific. It's been very difficult getting third-party libraries with Bitcode support, but Bitcode is required for watchOS 2 apps.

[1] http://streaksapp.com

I am using DAWG in my iOS word game, Hexiled[1].

It was pretty interesting to implement and sped up the real-time dictionary searches exponentially (from my original solution, which was a basic SQL LIKE match).

Additionally, Hexiled uses a number of languages, including with accented characters and this didn't have any negative impact on things.

[1] http://hexiledgame.com

iOS 7 (2013) introduced the GameController framework, an SDK to allow game developers to detect physical button presses / D-pad, etc...

This was designed to work in conjunction with hardware makers who made game controller shells that housed iPhone / iPod Touch, but with some extra physical buttons.

I always viewed this as laying the groundwork for an Apple TV App Store, but it seemed to instantly lose traction and haven't heard anything about since the couple of months following WWDC 2013.

I assume that API will gain some more steam now.

Author here. I self-published this book as a sequel to my previous book, The Definitive Guide to GTFS.

The first one is all about public transit schedules in GTFS format (used by Google, Apple and most public transit apps).

This one is about real-time data that complements the scheduled data (data such as vehicle positions, trip cancellations, etc...)

If you have any questions about transit, GTFS, or self-publishing, I'll be here all day!

Thanks for the feedback.

The real key is that you get stuff done when you don't feel like it. This rewards you for getting the smallest amount done to keep you on track.

The real progress is made when you do large amounts of work, but the small amounts keep you invested.

Also true of using Sqlite without CoreData in Swift

Thanks, appreciate the kind words.

We really tried to pull back the features as much as possible. We storyboarded complex stats charts, reports, being able to add in data for missed days, etc... but all that adds to complexity and technical debt

It looks to me both apps target the same mindset, but with slightly different execution.

Streaks limits the number of tasks and adds pretty icons, plus HealthKit integration, while it looks like HabitList puts a bigger focus on the reporting side of things.

Thanks - we had discussions about this exact issue. We wanted something that wasn't a checkmark in the icon.

We played with another variation for quite some time but it didn't indicate anything related to tasks/completing something.

I really like what Apple has done with the icon for iOS "Activity" app that accompanies the Apple Watch. That the conveys a similar message to what we're doing.

(I do confess: I've tap-held our app icon from Springboard a few icons, which enables the app wiggle for rearranging apps)

Thanks!

1a. I find "Regular" todo apps get overwhelming after a point. I know this because I have about 10 different todo lists that currently aren't being completed

1b. The other apps like Streaks I personally don't think are simple enough. Either they show too much information or they don't compel me to complete tasks enough. There is a real feeling of satisfaction in Streaks simply by having to press-hold for half a second to complete a task.

2. I'm not going to profess to any scientific studies. Simply put, this is what works for me. I've been using it in prototype form since early February to scratch my own itch in relation to the daily tasks I need to complete

Thanks - I hope you get value out of it. Would love to hear your feedback after you've used it for a little while.

Just looking at that site now and how they pitch their product, I would say the difference is in how specific things are.

Their example says "Get fit", whereas in Streaks you would have a task "Walk 5,000 Steps"

I upvoted you because I think it's good feedback.

In actual fact, Apple have just shown their hand with this with the Apple Watch daily goals. It's somewhat similar, yet I think both can co-exist easily.

In fact, I use both. Streaks doesn't rely on the Health app, but once the prototype was up and running it was clear the app was superior with HealthKit integration so it became a bigger part of the app.

Apple are investing heavily in the health-related aspects of iOS. Your argument could be applied to any app that integrates with the Health app.

(Side note: I also make public transport apps for iOS, so I'm well aware of how things can go, with all the rumours circling about transit announcements at WWDC)