- School District Builds Own Software — By taking a not-for-profit approach and using freely available open-source tools, Saanich officials expect to develop openStudent for under $5 million, with yearly maintenance pegged at less than $1 million. In contrast, the B.C. government says it spent $97 million over the past 10 years on the B.C. enterprise Student Information System — also known as BCeSIS — a provincewide system already slated for replacement.
- Giving a Presentation From an Apple ][ — A co-worker used an iPad to give a presentation. I thought: why take a machine as powerful as an early Cray to do something as low-overhead as display slides? Why not use something with much less computing power? From this asoft_presenter was born. The code is a series of C programs that read text files and generate a large Applesoft BASIC program that actually presents the slides. (via Jim Stogdill)
- AirBnB TechTalks — impressive collection of interesting talks, part of the AirBnB techtalks series.
- Gawker’s Realtime Dashboard — this is not just technically and visually cool, but also food for thought about what they’re choosing to measure and report on in real time (new vs returning split, social engagement, etc.). Does that mean they hope to be able to influence those variables in real time? (via Alex Howard)
What is Apple going to stick on our wrists?
By all accounts, we won’t be seeing the iWatch until sometime next year. This is giving the press lots of time to speculate about exactly what the device might be. Since I can wildly speculate as well as the next tech pundit, I thought I’d take a shot myself.
To start, we can pretty safely say what the iWatch won’t be, and that’s a standalone cellphone. As clever as Jony Ive is, he has yet to become master of the laws of physics, and the limiting issue for cellphones is the size of the battery. Most of the actual bulk of a modern phone is the battery, and even if an iWatch uses a power-miserly processor and display, the cellular radio itself is going to put too much of a drain on the device to make it practical. Consider that the Galaxy Gear (which is trying to steal the iWatch’s thunder by getting to the market first) lasts about a day between charges, and has no phone inside it.
Thanks NSA, you've spoiled mobile crowdsourcing for everyone else!
The continual drip-drip-drop of NSA secrets, courtesy of Monsieur Snowden, has provided many of us with a new piece of daily entertainment. But as much fun as it can be to see No Such Agency’s dirty laundry being aired in public, it has a real and lasting affect on how consumers are going to see interacting with their mobile devices. Specifically, it could provide a major setback to the new universe of applications that use crowdsourced data.
There are lots of examples of highly successful apps that are essentially just aggregations of user-provided data. Yelp comes to mind immediately, but another good example is Waze. In both cases, users are providing the service with some fairly private information, where and when they were at a particular location. Waze is even more sensitive, because it is also recording your speed, which might be a bit higher than the posted limits.
Forget Touch ID, we're still waiting for access to Siri!
As I mentioned last week, the new Touch ID feature of the iPhone 5S is (at least for the moment) only usable by Apple created software. What this means is that a developer can’t take advantage of the feature to authenticate a user inside an application, it can only be used to unlock the phone and authenticate to iTunes.
This continues a troubling trend we’ve seen with Apple lately. Nearly two years after the release of Siri, the voice UI is still locked out for anyone but Apple and their chosen partners (such as Wolfram Alpha.) I understand that opening up a technology for third party usage takes planning and work, but twice in a row now, Apple has released what could be a transformative technology, and left the developer community out of the picture.
Even a great development environment has room for improvement
As the not-so-mysterious September 10th Apple event approaches, it’s widely anticipated that the final version of iOS 7 will be released at the same time. Along with it will come a new version of XCode. While XCode is a pretty awesome development environment (in my opinion, at least), there are a few things that just irk the heck out of me. So, if anyone at Apple happens to be listening, here’s my laundry list of things I’d like to see fixed.
The App Store model has increased the uncertainty of the software release process
The recent unavailability of the Apple Developer’s Portal just underscores how increasingly dependent developers have become on third parties during the software lifecycle. For those who are not following the fun and games, the developer.apple.com sites, which include much of the functionality needed to develop Mac and iOS applications, has been unavailable for more than a week as of this writing. Although iTunes Connect, the portal used to actually deploy apps to the App Stores, has remained available, the remainder of the site territory has been off-limits. This is all thanks to a security intrusion (evidently by an over-zealous researcher.)
The App Store model has fundamentally changed how software is distributed, mostly for the better (IMHO), but it has also removed some of the control of the release process from the hands of the developers and companies they work for. As I have spelled out previously in my book on iOS enterprise development, the fact that Apple has the final say on if and when software goes into the store has required more conservative release timelines. If you want to release on the first of September, you need to count back at least two weeks for “gold master”, because you need to upload the app, potentially go through a round of rejection from Apple, and then upload a fixed version.
Android apps don’t suffer from this lag, because most of the Android stores don’t do any significant checking of the applications uploaded to them. The Devil’s Deal that Apple developers have made with Apple is that in return for the longer wait time to get apps in the store (and having to follow Apple’s rules), they get a de facto seal of approval from Apple. In other words, it is assumed that apps in the iTunes store are more stringently policed and less likely to crash or do harm (deliberately or else-wise.)
The current downtime has brought that deal into question, however. Suddenly, developers who need new provisioning certificates, passbook certificates, or push notification certificates find themselves with nowhere to go. Even if iTunes Connect is available, it doesn’t do you any good if you can’t get a distribution certificate to sign your app for the store. I’m sure that there are developers at this moment who have had their finely tuned release strategies thrown into disarray by the in-availability of the developer portal.
Being essentially at the mercy of Apple’s whims (or Google’s, for that matter) can’t be a pleasant sensation for a company or individual trying to get a new piece of software out the door. The question that the developer community will have to answer is if the benefits of the App Store model make it worth the hassles, in the long run.
Worth the Blood, Sweat, and Tears?
Joshua Smith (@kognate) is a Lead Mobile Developer at iRx Reminder, frequent Cocoa Conference speaker and author of an upcoming book with O’Reilly on core data. We recently sat down to talk about core data and its complexities.
You can view the entire interview in the following video:
If Jenkins is good enough for Apple to use, why not give it a try yourself?
One of the pleasant surprises I learned last year at WWDC is that Apple uses Jenkins to automate their iOS app builds. Since we were already using Jenkins to do the same thing at the Day Job, it was a nice confirmation that we had taken the right approach.
However, until recently, getting Jenkins to fire off an Xcode build, bundle it into an IPA, and sign it correctly was a real pain. Thankfully, in 2012, a Jenkins plugin for Xcode integration was released. It can be installed directly from the Jenkins plugin management page, and once installed, gives you a new build step called Xcode that you can add to a build.
School District Saves With Open Source, Apple ][ Presentation Tool, Tech Talks, and Realtime Dashboard
New PayPal partners, mobile wallet disruption may hinge on Apple, and prioritizing mobile in a "lukewarm" market.
Here are a few stories that caught my attention in the commerce space this week.
PayPal expands its footprint with new partners
PayPal announced this week it has expanded its U.S. footprint to include 23 new partners for its PayPal in-store payments service, in addition to the 15 national partners announced last May, making its service available in 18,000 physical store locations across the country.
According to a post on the PayPal blog, new retail partners include Barnes & Noble, Office Depot, Foot Locker and Jamba Juice, and “two additional partners that [they] will share publicly soon.”
The deal PayPal struck with Jamba Juice goes beyond the in-store payments service that allows customers to pay with their phone number and a pin, or by using their PayPal payment card. Chloe Albanesius reports at PCMag that PayPal is testing its PayPal App in one Jamba Juice location to allow customers to place and pay for their orders, so when they arrive at the location, they just have to pick up their smoothie.
Global product VP Hill Ferguson notes in a post at the PayPal blog, that the feature is available only for iPhone users at this point and that there are plans to expand to more Jamba Juice locations this year.
In addition to its announcement of new retail partners, PayPal also announced a new hardware partner. Sarah Perez reports at TechCrunch that PayPal is “also partnering with point-of-sale and hardware maker NCR to expand into restaurants, as well as into other businesses, including gas stations and convenience stores.”
Apple may yet embrace NFC, mobile shopping isn't a fad, and will the mobile wallet battle come to a head in 2013?
Happy new year! Here are a few stories that caught my attention in the commerce space recently.
Apple NFC rumors revived
We’ve no sooner outfitted our shiny new iPhone 5s with cases and fancy accessories than rumors of the iPhone 6 have emerged. Matt Brian reports at The Next Web that “Apple has been testing hardware relating to a new ‘iPhone6,1’ identifier, powered by a device running iOS 7.”
There’s also renewed rumors of Apple’s intention to integrate NFC technology into the next iPhone. Mikey Campbell reports at Apple Insider that on December 20, 2012, the US Patent and Trademark Office published a patent application filed by Apple in 2011 “for an ‘Integrated coupon storage, discovery, and redemption system,’ a property covering the receipt, storage and use of digital coupons on mobile device” — basically, what Passbook became this past year. Campbell notes that NFC capabilities also are mentioned in connection with coupon redemption, indicating “that the company is at least thinking about including the protocol in future versions of the iPhone or iPod Touch.”
Joann Pan at Mashable notes the implications such integrated technology could have on retail shopping for consumers and merchants alike. She writes:
“With Apple’s proposed ‘integrated coupon storage,’ patrons will be able to walk into stores and receive notifications about items for which they have coupons. After the transaction is complete, the customer will receive a digital receipt wirelessly. Alerts will also be pushed for coupons with impending expiration dates. The patent also mentions a verification system for coupons and discounts.”