Developing the Ecolabel Index
Tuesday, August 17 2010
We are pleased to have shipped some of our finest work to date, for the Ecolabel Index, a global database of ecolabels put together by Vancouver-based Big Room Inc.
The Ecolabel Index aims to make the universe of information about ecolabels, including some very important details for consumers, available and useful. Everything from the ecolabel's standard, sponsoring organization, how compliance is audited, and how the ecolabel requires improvement over time. All of this, and more, is available for ecolabels we see and use every day.
The work was a migration away from a Drupal and Apache SOLR installation onto a more stable, more secure, and more maintainable platform. We reproduced nearly all the features of the former site (ecolabelling.org) and laid the foundation for some exciting changes Big Room has in mind.
The work involved data modelling in PostgreSQL, carefully crafting the markup to ensure an accessible, standards-compliant experience, integrating a variety of subtle effects from the YUI interface library, and semi-automatically extracting their site's content from Drupal's disaster of a data model.
The site's design was put together by Trevor, who seems to reveal a new-to-me talent every week. HTML craftsmanship by Paul Tichonczuk of Digital Dream.
We enjoyed tremendously working with Trevor, Jacob, and Anastasia. Check out the Ecolabel Index for yourself!
Written by Stephen van Egmond | permalink
Apple updates its SDK
Thursday, July 15 2010
Apple continues to tweak its SDK licenses.
The controversial section 3.3.2 before:
3.3.2 An Application may not itself install or launch other executable code by any means, including without limitation through the use of a plug-in architecture, calling other frameworks, other APIs or otherwise. No interpreted code may be downloaded or used in an Application except for code that is interpreted and run by Apple's Documented APIs and built-in interpreter(s).
after:
3.3.2 An Application may not itself install or launch other executable code by any means, including without limitation through the use of a plug-in architecture, calling other frameworks, other APIs or otherwise. Unless otherwise approved by Apple in writing, no interpreted code may be downloaded or used in an Application except for code that is interpreted and run by Apple's Documented APIs and built-in interpreter(s). Notwithstanding the foregoing, with Apple’s prior written consent, an Application may use embedded interpreted code in a limited way if such use is solely for providing minor features or functionality that are consistent with the intended and advertised purpose of the Application.
3.3.9 You and Your Applications may not collect, use, or disclose to any third party, user or device data without prior user consent, and then only under the following conditions:
- The collection, use or disclosure is necessary in order to provide a service or function that is directly relevant to the use of the Application. For example, without Apple’s prior written consent, You may not use third party analytics software in Your Application to collect and send device data to a third party for aggregation, processing, or analysis.
- The collection, use or disclosure is for the purpose of serving advertising to Your Application; is provided to an independent advertising service provider whose primary business is serving mobile ads (for example, an advertising service provider owned by or affiliated with a developer or distributor of mobile devices, mobile operating systems or development environments other than Apple would not qualify as independent); and the disclosure is limited to UDID, user location data, and other data specifically designated by Apple as available for advertising purposes.
Written by Stephen van Egmond | permalink
Proposal: Toronto iPad testing group
Monday, April 19 2010
One of the biggest problems iPad developers face is getting their applications tested on working devices. With an iPhone, that's pretty easy - with millions sold, developers have a ready set of willing test subjects.
However, with Apple delaying its release of the iPad into "sometime in May", Toronto's developers are a bit screwed.
We're willing to put together an iPad / iPhone testing group. You can get your apps tested as long as you test others' apps. What does that mean, concretely?
- We will allocate 75 slots on our Apple developer account for testing circle members.
- We'll maintain a code-signing profile that all members can download, and let members post binaries built against that profile.
There will be an emphasis on transparency within the testing group, so the list of members will always be visible to participants.
The obvious concern is going to be about disclosure of sensitive information. All I can promise is that if someone violated the implied trust of this community, they are in for the wedgie of their life the next time they show up at @coffeeandiphone. Otherwise, no guarantees.
It wouldn't be free. We'd collect some nominal fee to cover our costs developing the plumbing for this.
Please send your thoughts by email to dev@tinyplanet.ca or by Twitter to @svanegmond .
Written by Stephen van Egmond | permalink
An app to call our own
Tuesday, April 13 2010
We routinely ship work for our customers, but it's nice to do something for ourselves every once in a while.
Public Opinion, our first app for the iPad, is now available in the Apple Store. Learn more at opinionapp.net.
Written by Stephen van Egmond | permalink
TTC Panel: Restart the ecommerce project
Friday, March 05 2010
With the announcement of the TTC's customer service advisory panel, I thought I would offer my own suggestion for low-cost improvements to customer service:
Restart the e-commerce project.
The e-commerce project is a simple, low-cost, high-benefit project whose main purpose is to modernize pass purchasing: customers can buy passes with a web browser or a mobile device, anytime they want. No more waiting in line at booths.
This is not even a new project: the TTC issued a competitive RFP in August of 2008 which a number of companies, including Bell, responded to. In October 2009, my company - Tiny Planet- was awarded the contract.
We lasted 21 days between getting the purchase order (the legal start point of our work) and the Commission meeting of October 29, 2009 where the e-commerce project was moved below the funding "line" along with a laundry list of other improvements, from station modernization to replacing the vehicle position-reporting system.
The list of deferred work looks like this:
(source; page 19)
That's us at the bottom of the first list, pushing the total value over $600M.
(Lest you think we're charging the Commission $800k for an e-commerce site, please note our fees are a very modest fraction of that figure. $0.8M is our fees + the TTC's costs to build their end of things, and operate it for three years. There's a mobile application in there too. All for less than half the cost of the project to install debit/credit card machines at every station.)
Customer-visible improvements aside, this project will also provide the TTC's staff with a better understanding of the realities of running an electronic payments system that can be accessed by the public. Typically, online transactions see fraud rates between 4% and 10%. Part of our job is to build up the TTC's countermeasures and institutional understanding of electronic fare payments.
So in summary, this is a project that:
- is relatively cheap.
- has already been through a competitive tender.
- provides clear customer service improvements.
- can be restarted by a Commission decision.
Why not restart it now?
The project is on hold and can be restarted until June 30, 2010, after which time it can be (will be?) cancelled.
Customer service panel: recommend this project be restarted.
TTC Commissioners: don't wait for them to recommend it.
Written by Stephen van Egmond | permalink
» Archives
