Situation
A 2012 iPhone game that had to ship: a horror runner, told as a story, with a dark visual style.
Shipped work · iOS development
Curio
An iPhone game Jon helped develop in 2012. A contemporary review described it as a horror runner set in an asylum, with a narrative and a dark art style.
Shipped iPhone game, 2012
Shipped work.Named only to the extent the credit is accurate. No rankings, download counts, or invented titles.
MashButtons, January 2012: “Curio: Equally Frustrating and Addicting”
Outcome
Curio shipped. Jon helped develop it. A January 2012 MashButtons review is the public write-up. This page does not add download counts, chart positions, or a job title beyond that.
Curio is an iPhone game from 2012. Jon Higgs helped develop it. That is the claim this page makes, and it stops there. No lead title, no studio credit beyond development help, and no App Store numbers.
A review published by MashButtons in January 2012 described Curio as a horror runner set in an asylum: narrative, a dark art style, and a difficulty the reviewer found both frustrating and hard to put down. The review is about the game. It is linked here so the description is not invented on this site.
Read the MashButtons write-up.
The practice around that work is iOS development: a defined app, carried through as a project. Curio is evidence that an iPhone title has shipped with Jon’s help. It is not an offer to start a game studio, and it is not a promise that the next engagement is a game.
Related practice: iOS development
Other examples
- Siebel 7.8 to IP2014, with Open UI and AWS environments — Siebel CRM
- Public Sector case management for a state attorney general — Siebel CRM
- VB6, AngularJS, and WebAPI in the automotive aftermarket — .NET applications
- Siebel membership pricing, then .NET, WCF, and SharePoint — Siebel CRM
- Two Siebel views, one order — Siebel CRM
- The billing app only one person could change — .NET applications
- Drafts beside the CRM, not a new system of record — AI consulting
If the system matters and the team is small, start with a conversation.
A paragraph on the system, the constraint, and the timing is enough. Jon reads these. There is no intake desk.