Wednesday April 11, 2012

Year 3

Well year two didn't go so well from the point of view of blogging. It wasn't a requirement and the way things dragged on I wasn't sure how I'd post anyway. Year 2 had ups and downs, mostly downs, so I'm starting fresh with year 3 and I'm doing this for my own learning. I'll revamp the look of the blog at some point but that will be a time-consuming and it's rather low-priority.

In year 2, the 6 papers I did were:

Studio 3: A semester-long project called species recognition. My team was to build a magic box that could identify species roaming the forest floor for the Department of Conservation. We built *something* despite the internal issues we faced (team dynamics, we should probably have split apart early in the piece in hindsight).

Theories and Philosophies of Technology: A series of lectures looking through the ages and how technology and our view of it has evolved. It culminated in an essay of sorts, a discussion between two people about technology.

Smart Systems: Was basically arduino-based with an end project to build a smart system. I teamed up with one other to build a system that monitored so aquaponic plants and adjust lighting, temperature and water pumping based on timers.

Studio 4: I pitched a project of my own, a security system that utilised social networking, creating a virtual neighbourhood watch. We had grand plans but were tripped up by the two other papers taking more than their fair share of time and equipment that didn't work because it was cheap (a knock off android tablet was the worst). Also our team was pushed into delving too deep into the conceptual side when all we really wanted to do was create a working product.

Intellectual Entrepreneurship and Innovation Management: This was sort of a business paper, we learned what an Entrepreneur is and looked into creative innovation. We had 3 projects, one a presentation as a group on a theory of group dynamics, another was a personal 3 minute video selling ourselves as an entrepreneur, and the last in the same groups, come up with a technical innovation, turn it into a product and try to sell the idea to a Dragon's Den. Real funding was up for grabs if the idea was good. However, once again we had group issues, and a couple of us (me included) felt flat and disappointed and didn't believe in what we were selling. A couple others were passengers. It also took WAY more time than it should have and helped kill Studio. I'm still mad about that.

Simulated, Immersive and Interactive Environments: We looked into the idea of using patterns to create a computer game. It seems that's how we'd have probably done it anyway to a large degree but the goal was to explore pattern design as written about by Christopher Alexander, an Architect. At the end we had a mostly working game. This was also a painful paper. We made the game in C++ Visual Studio using the SDL library (an api for sound and graphics). However no one had ever really done much C++ programming. I was fortunate enough to have started teaching myself C earlier in the year but that mostly just made me aware of how little I knew. I have no idea what other class members made of concepts like pointers when they weren't really aware of them.

So... pretty blah year, and I was glad when the holidays started.

This year I'm doing 2 external papers and 2 new internal ones. Studio 5 and 6 are one project but with different milestones. I'll explain it all in upcoming posts, but for reference, my papers are:

  • Digital Cinema Studies (External)
  • Animation and Moving Images
  • Studio 5
  • Digital Audio Production (External)
  • Emerging Practices
  • Studio 6

    Friday April 20, 2012

Studio Y3


    Thursday May 3, 2012

Dating & Social Networks

I have had a very very slow start to the year with Studio and it was getting me down. In Year 3 we must come up with our own projects, and they will be a year long. I had been fortunate enough to have been warned a few weeks before we started semester that this would be the case, and really, it was something I was half expecting anyway. But I still wasn't really prepared. My team mate from 4 projects in a row starting from midway through year 1, Anneke was quite down about how last year went (as a lot of us were) and she was non-committal about everything. When I revealed my idea for a web application, a type of social calendar, she really didn't want to do it. Her two reasons were that she was sick of doing techy things that were beyond her skill set (I don't think that this really was, but last years project was though) and that she wanted to come up with her own ideas. I didn't pursue it any further but was a bit bummed that our working relationship was about to end. She was one of the few people that I really liked working with and worked well with. And because of that I didn't really look elsewhere for partners. I presented my idea to a new tutor who understood it well and said it was a good engineering project but BCT of course is also conceptual and because of that I'd have to work out a question and perhaps I could plumb my solution into the answer of that question or maybe I'd find something else. An example might be "how can cloud computing aid social networking?"

I understood this and drafted a presentation together. I mentioned Facebook and Google Plus and the original idea and it was a bit of a muddle. But it bought me time and I could think about it further. The feedback I got wasn't wonderful and I found that disheartening and I really wasn't feeling the project anyway. I had doubts about my calendar, and decided I cant be bothered making predictions about social networking. Especially now that Facebook is like... Microsoft. Crap, but big and business saavy enough to survive regardless. I was enjoying Digital Cinema Studies and that paper also had things to do. Where as Studio is always waffly to begin with. And if you don't know what you are doing then it's even more waffly if that is possible.

Also a social calendar has been done before (though nothing like I was planning originally), I just can't see how to get something like that to a tipping point of usage. I don't really think I care about organising other people's time either. I hardly organise my own time and I'm not sure I can be bothered working out how a tool world make me use it or help me. It's... boring.

So 5 or 6 weeks in I still had nothing really and was very down about it. I skipped a formative assessment because I had nothing to present. Well it turned out I wasn't the only person to do that and plenty of people who didn't skip had nothing decent to present either. Not that this really helped me, but at least I wasn't alone. The following weekend I decided to change to something I had been working on for a few weeks prior to starting this semester.

I hadn't been able to get work in my previous industry (if I'd told potential employers that I wanted to work there for years, not a few months until I went back to uni, I'd have had a job. Too honest for my own good it seems). I decided to build a website. I had a few website ideas, but this one was something I'd thought about previously but didn't have the skills to execute. But I was desperate for money. Alas I didn't just build some quick and dirty site, I spent a lot of time on one part of it then semester started so I shelved it. What was it? A dating website.

Now, it's not going to be a straight build a dating website and hand it in. That is not a BCT project. But I have questions, many, I can ask. And I can explore avenues. I can explore avenues that I wouldn't bother with if it was a home-job. I'll get more into that soon. But this is my basic project, build some kind of dating website or social network that is fun to use and solves some current problems that exist within the current crop of sites.

    Sunday June 24, 2012


Well this semester's blog got neglected. I didn't have much new to post anyway. I had concepts that I wanted to develop. I wish I had actually done so a little earlier too. I can't say that though, Digital Cinema Studies sucked too much time and that is the way it was. Out of my hands somewhat. Screw group work in electives, it's always a formula for sucking more time than you have, and sucking it away from stuff that is worth more. Like Studio.

I wanted to get back into iPhone application development but wasn't sure how, I'm building a website after all. Somewhere along the line, I had an idea for a location-aware dating service on the iPhone. I fleshed out the idea in my head and mentioned it to a class-mate and former team member of one of my good-group experiences in BCT, Lidy. She quite liked the idea and equated it to a sort of speed dating. The idea was basically an app that knew your location and allowed you to meet up with other registered users over a coffee break. I discussed it - over coffee - with Lidy and Anneke a couple of days later. I love bouncing ideas off them. The idea then sat around in my head for a while as I had to fight fires with Digital Cinema Studies and hand in an animation assignment in a complex program I'd never used before called Maya....

As semester end drew near I realised it might be more prudent to spend my remaining time collating all the dating website research I had done into meaningful thoughts and writing. I then built a presentation, a contextual statement (which then made me change my presentation) and then try to build the application. Of course time was running out and building a whole application from scratch when I haven't used XCode / Objective-C for 2 years (and XCode has changed significantly in that time it turns out) was a bit ambitious. I built a basic storyboard for it and a couple of iterations of designs but they really need more work and then I had to create other hand-in material. I really want to make an exhibition of quality, but this semester wasn't going to be it. I had neither time nor money nor a working application. I settled for a poster. I think my idea was strong and there was a lot of of background to it. But I can do an order of magnitude better. Though for that to happen there need to be certain conditions met which weren't... Next semester I'm going to blow everyone away.

It will be interesting to see the results of this semester though.

Oh yeah, the application is called (currently) CoffeeDate.

    Saturday July 7, 2012

What it takes to make an iPhone app

I'm nearing the end of a 3 week break. One more week to go. But I haven't been totally relaxing, I've been learning (again) Objective-C and Cocoa. First I started storyboarding CoffeeDate, the application I'm building. I removed all of the custom graphics which were distracting so I could concentrate on it's functionality. I had used some code to create a table view that I had pulled off the net for the purpose of demonstration in my presentation, but the code had a small part that was specific to the storyboard setup in the example that it was demonstrating, and quite different to mine so running it resulted in a crash. I couldn't penetrate the code even with the explanation in the tutorial and once the presentation was over I decided to relax and step back a bit. I took the offending code out and started reading an online book on Objective-C. I then moved onto  the next book from the same website on iPhone application development, following along the tutorials. I got half-way through hand decided I should be able to muddle along a bit further with my app. I did, but quickly got stuck and wound up reading a lot of Apple's iOS documentation. I've found the syntax of Objective-C a bit of an obstacle in learning, being more familiar with C++ syntax which every other language I've learnt tends to be closer to. Also the higher level concepts are difficult to follow. I find that material on Objective-C either deals with concepts on too much of a high level for me with loads of opaque jargon, or it goes right the other way dumbing down explanations with awful analogies. Where is the middle ground? I am quite willing to get right into advanced stuff. Just start with the background first. I almost wonder if it would be advantageous to write a "book" of my own on Objective-C, so I could explain the concepts to myself. Then when it was done I'd also have a rather good book that I could sell.

I'm currently zipping through a real book on Objective-C for beginners, trying to glean basic info that I may have missed. One utterly confusing thing was when it tried to explain the concept of Polymorphism and took an entirely different approach to the more standard explanations. I'm not sure how the different explanations marry up. This brings me to something else, I suspect that some of the names, terms and concepts sound really big but aren't quite that important to actually have their own name in practice. If they are, perhaps explain why it's so significant. Some history please. Lets use the example of Polymorphism which as I currently understand it is simply the ability for different classes to each contain a method that has exactly the same name. It's almost a Whoopy-doo in some ways. I mean, why the hell wouldn't you allow 2 or more entirely different classes to re-use a name? So for (real-life I did this once) example, if you were making Pong and you had a class called "Bat" and a class called "Ball" and a class called "Score" they could both have methods called update and update could work completely differently in each. Update in Bat and Ball might update the movement while update in Score will check the score and update accordingly. Well the explanation in this beginners book I think is basically saying that... well I don't know what it's saying. It literally says " the ability of an object of once class to appear and be used as an object of another class". Whaa? The example doesn't shed much light but thanks, I thought I knew what polymorphism was until I read that.

I just looked it up on Wikipedia and it appears that there are a few different definitions of Polymorphism but only one in the context of object-oriented programming. And it is essentially the same method name in different classes. Though now I'm not sure if it relates the the fact that the method could be from superclass. Ugh. Though that wouldn't make sense with my original explanation which I really think is the most accurate so far. So you can see why I'm confused. Most computer types just seem to like big words, perhaps over compensating in some way.

So why would Polymorphism be isolated as this grand feature when you'd kind of expect things to be that way anyway? Well I can think of 2 possible reasons: One reason is that being aware of this concept  means you'll use it in an advantageous way when designing code. If 2 methods in 2 different classes essentially do the same thing (though not entirely in their implementation) you will actually be inclined to name them appropriately. The other reason is that you couldn't always do this, so when you could, it became a feature.

So, a real programmer (or me one day in the future) may read this and cringe at the above.

Anyway, as you can see, learning iOS development is a bit of a struggle. Yet lots of people do it so I'll keep going.

    Sunday July 22, 2012

Semester 2

We've been back one week and had to discuss the direction of our projects with tutors. Like the majority of the class I was asked to re-frame it in some way and I managed to talk to 2 tutors to get some idea of what that meant. My impression is that I need to develop it any my questions further which is kind of what I intended to do anyway fortunately. Not just continue working on it but develop some of the ideas behind it, do more research on last semester's findings and somehow find a way to position it within the context of dating and social networking. I've just finished writing a presentation, I'm not really planning on presenting anything visually because the entire class has to present tomorrow. That's a lot of people. I've written an A4 page worth of presentation and it's helped me develop my ideas further.  Depending on how much time I have I might re-think this.

    Wednesday August 1, 2012

What the hell have I done...

I have a couple of weeks break from learning Xcode for a few of different reasons. One I was getting sick of it, two I was actually sick in bed, three, a friend needed my help to do a project that used After Effects (fun when you are sick btw) and four, we had to represent our projects anyway. This small break made everything I had learned fall out of my brain and it all became rather opaque again. I don't know why Objective-C and Xcode is so difficult to pick up for me. Well, actually I can tell you exactly why - it's syntax is completely different for starters - but I don't know why that is causing me so much grief. People code in Objective-C all the time. Some of them didn't know how to code before that. Kids chewing chewing gum into their microphone do youTube tutorials (though I suspect some of them don't quite get what they are doing in any depth, but they can still successfully mimic code that works and make something that works). Anyway this is just me venting because progress has been slow... well, non-existent really, the last 2 weeks. It's not all because I can't do it though I've had a bunch of life obstacles this past week that have really gotten on my nerves. One of them kept me from sleeping at all last night so this afternoon as I try to take in someone's idea of how to do a login form (should be so simple), I can't actually concentrate. So I'll be needing a sleep before I do any more real work I think. Vent over.

    Saturday August 4, 2012

Break through, but new challenges

The day after I wrote that post I had some downtime in a part time job that I do for the university (iPad support for staff, it's handy, I get an iPad to use out of it) and I looked into whether one could request location data from within Safari (which I thought must be possible on and iPhone, it is possible everywhere else after all) and yes you can and yes it's very easy. This suddenly got me thinking about how I could implement v1 of this app using a web technology instead which would enable me to actually get something working really quickly. So I got excited by this prospect and started working on it. This is of course ground that is well covered in development circles but it's all new to me. In the process I have discovered the things that I can't do easily. One is access the camera or the camera roll. There are ways around it, but none are elegant. iOS6 however will enable which is what I'm looking for. But that is iOS6... That isn't released until September some time (probably) and then there is the take up. Fortunately on the other hand, Apple devices tend to get updated. Unless the device doesn't support it the upgrade. I'm a bit puzzled why the iPad 1 isn't supported for example, not that it affects me.

Happy with this revelation about creating a Webapp that could possibly work enough for testing until I can make the native app, I decided to go down the route of actually buying an iPhone. Not an expensive one. Just a 3Gs. That will support iOS6, and I have a friend with a 4S so I can test applications on 2 different models of phone. The decision to buy an iPhone only came about because I was discussing running, mp3 players, the Nano with it's pedometer with a friend (Lidy) who then pulled out her iPhone with a GPS-enabled running app and all her running data. I managed to find a bargain on Trademe so swooped in. Hopefully it will turn up in the next week and I can use it to text my application (and for running with).

I've managed to book meetings with just about every tutor over the next 2 weeks so I hope I'll have something to show them before then and I can concentrate more on other issues.

    Tuesday September 11, 2012


I haven't been here for a while yet I've done so much. I still have a broken web application though. I'm stuck on creating a persistent session on the webapp. Information is thin. Well, if I was content to just sit and read loads of different tutorials or buy a comprehensive book on the subject I might be able to achieve it. I never feel I have the time to do that so I just try to muddle through.

I think I'll make more and shorter posts because so much information about what I've been doing relating to this project has been lost in regards to this blog.

I started creating a web application from scratch, then wondered how I'd turn radio buttons into segmented controls through styling. It turned out to be a bit difficult though not impossible and eventually I found my way to JQuery mobile which I started using to create the app. They've done all the hard stuff for me so I can concentrate more on just making the app. But it still wasn't plain sailing, I've written most of the PHP myself and I sort of wish I'd used some sort of framework for that too. But it's too late now I think. Maybe not... never know which path to take, you just have to go down one and stick to it. Last time I worked on the app I had quite a few bugs that resulted in a page loading into the app that simply said "undefined". Really helpful. I really dislike rushing along because of deadlines, I could do this so much better if it wasn't a uni project. I also have a load of conceptual and academic ideas on this project but I haven't written much down. I'm going to start a contextual statement in the next day or so. I just want to reach a milestone where sessions for example works. The path is slow.

Today I've picked up the app for the first time in over a week. I took a break from it to do other stuff. I hoped that doing so would clear my head somewhat. Not sure it has. PHP sessions don't seem to persist once a user has left the app for the home screen so they have to log in each time. So I'm looking into how cookies are set for sessions.

    Tuesday September 11, 2012


Goddamn this undefined error is getting on my nerves. It doesn't matter what I put where to catch the error it still pops up. For ages I wasn't even sure what was generating it. PHP? Javascript? Today the finger was potentially pointed at JQuery Mobile. I think I've isolated it to a single PHP statement that shouldn't be causing any problems because the objective of this statement is to catch undefined variables!! This is driving me nuts, I really don't have the time.


I just figured it out. It IS JQuery Mobile. It didn't like a function that is supposed to redirect to a page on an error. I've worked around it by taking the function away and putting a html message and okay button which links back to the page instead. Seems redundant but at least I can get on with things. This error will be scattered all over the place because I did a marathon session a while ago and implemented it everywhere that it would be needed. I just need to change everywhere now.

    Tuesday October 9, 2012

Dev World

I had a slight interruption to Studio and everything BCT; I went to Melbourne on a Scholarship to Dev World. Run by what was formally called the AUC (Apple University Consortium), it's a bunch of Australasian universities who pool their resources together and create events and seminars, other notable events are Create World. So Dev World is a developers conference mostly geared towards Apple development. However Apple has withdrawn itself somewhat and this might have been the last Dev World of it's kind. There were a lot of talks on various aspects of development for iOS mainly and also web technologies. I got something out of it plus the opportunity to see Melbourne which is a very nice city. I was however a little worried about my Studio work and that we had a formative assessment a week later. But it was a great experience.

    Tuesday October 9, 2012

Final Formative

We had a final critique session last week. I seemed to have a few breakthroughs and spent many hours building the registration, the location awareness and writing that to the database and then the listing of people nearby. As the assessment loomed closer I kept working on the app. I should have perhaps worked more on some of my conceptual underpinnings of the project, but I really wanted to be able to demonstrate the app. I spent a lot of time scratching my head and searching for answers to bug that just should not have been happening in the first place. Some really basic form validation to make sure that certain fields (username, password and email) were actually filled out. Further validation was done on the server, but javascript took care of the initial validation. It kept returning false (saying they weren't filled out) no matter what I did. I tried so many different things and the code should have worked. So I sort of suspect the bug wasn't mine. Not the first time this has happened, I couldn't get user authentication to work properly and I think it boils down to Mobile Safari and something about it's cookie handling. Despite these problems I worked around them to produce something that sort of worked to a script and I demonstrated it. I also cobbled together my many thoughts on the app and the landscape surrounding my reasons for producing such a thing and some of the non-development research I've been doing. I'll post more on that a bit later.

The crit went rather well.

    Tuesday November 6, 2012

Studio Contextual Statement

This is a long one. I had to post my statement here as well as submit hard copy. The original had references but I've taken them out here.

Coffee Date - Contextual Statement

(Kitchen sink version, 5,760 words)

CoffeeDate was an individual project, as such I conceptualized and executed every facet of the project from beginning to end. I did however take on board suggestions, ideas , thoughts, discussions and input from tutors, friends and classmates. Sometimes incorporating that feedback wholesale or in part to experiments, tests, iterations or even the final outcome of the project. Ideas people gave me ranged from conceptual, theory or even technical or implementation.

Technical Considerations

In order to achieve the application itself, an iPhone app, I needed to learn to create applications in Objective-C and Interface Builder on the Mac. More specifically I needed to learn how to send information to and pull information from a remote server, implement a secure registration process and login process, a chat client, use location services and table views. However the project was not about just creating an an iPhone app and when it became clear that I risked spending a semester learning how to build an incomplete application, I explored the possibility of implementing CoffeeDate as a web application. It turned out that iOS supports web applications quite thoroughly an it was a feasible solution. Along with ease of development, this also bought with it other advantages such as the application being cross-platform, clients always being up to date and not having to submit the application to Apple’s app store.

Creating a web application is not simple either though. I still needed to create the backend, using MySQL and  PHP and then I had to create the pages that would be served up as screens on the mobile phone. While I have some experience in web development, I am not and never have been a web developer. This project required me to learn about SQL and PHP. I wanted to create an interface that was both visually and functionally similar to a native iPhone interface but there are elements that simply do not exist in the web world. For instance, the segmented control on the iPhone has no visual equivalent on the web, though it is functionally similar to radio buttons. Because of this I chose to use radio buttons and style them later with CSS. I created the bare bones HTML of the first registration page and was left with a nagging feeling about styling of the radio buttons. I didn’t want to move on until I knew how it could be done, in case it couldn’t. The search for a method of doing this consumed several hours before my search took me to JQuery Mobile. This was a Javascript framework that abstracted certain workings of a mobile web application development (namely the interface) away from the developer who could then concentrate on developing the actual application. It provided the segmented control with clever use of CSS and Javascript and I was able to move further on.

Essentially the application is built on HTML (5), CSS, Javascript and JQuery Mobile, certain proprietary extensions in mobile Safari (in order to get a splash screen and app icon), PHP 5.3 and MySQL. I used Dreamweaver to code with and MAMP for local testing sever development. I purchased an iPhone3GS to test the site on (This is not the only reason why I purchased it of course, but it certainly helped me to make the decision). With anything I didn’t know, I adopted mostly a “learn as you go policy” aware of the limited time I had available to me. The look of the app and the artwork used in the app icon and splash screen were - and at the time of writing still are - only for proof of ability to execute, and very much subject to change at a later date.

I’ve had to learn a lot about various technologies, but there is a lot of room for improvement. The PHP is messy and could do with being rewritten into classes. It does however currently perform it’s function.

Conceptual Framework


The project has evolved somewhat over the year and different things have interested me at different times, though some things have remained constant. On a purely technical level, I just wanted to build a dynamic and secure website that used a database and had users. Dating websites also interested me in particular because I joined 2 New Zealand sites briefly in early 2009 and what struck me was that for such popular websites they were either ugly or lacked what seemed like rudimentary features. One example is that filters were not reciprocal. So if a user ruled out a specific demographic for example, that didn’t stop that demographic from seeing and bothering that user. Another thing that immediately stuck out to me was that one could find people that they knew on the site and I considered that this might not always be something that a user wanted. I considered that if one could log in using Facebook then the site could automatically hide Facebook friends from each other (and state clearly that that’s all it was going to do). It was this initial experience and that at the time I wanted to move on from my current occupation that first made me consider building an alternative dating website. I felt that I could implement better features and a “nicer” user interface, though my web development skills were basic and as a worker with already did a technical job in a different industry. I didn’t feel up to spending my free time learning more technical skills for something that might never come to fruition. I valued my free time for other and more social pursuits.

Starting this degree enabled me to pursue a range of other skills however. The project became incredibly interesting as I read various articles and forum posts from sources with certain credibility such as, otherwise known as Hacker News. y.combinator is a seed accelerator, it incubates startups, provides advice and investment in return for 6% of the company equity. The forums attract entrepreneurs, programmers and tech pundits. Over the years there has been no shortage of discussion on what makes a good dating website, what the problems are with dating websites and various models they are based on as well and many outside links to other articles and discussions. This was a great starting place and provided me with a huge list of ideas for improvements of a theoretical dating website. I was able to compile a basic list of what seemed like fundamental flaws that prevented dating websites being effective for their users. I presented these in semester 1, but in the interests of completeness, I’m going to summarise my findings here: 

Dating websites reduce people into attributes that will fit into a database. This is the criteria users will search and can be searched on, so it becomes important data even though it’s not really the data one may use in real life. This creates a certain amount of superficiality. Other interesting things that were clarified for me included that sites with their anonymity promote misrepresentation and bad behaviour. Another interesting aspect of the sites were because they were dating focused, they caused users to concentrate on some sort of endgame rather than just talking to people and getting to know them. The experience was terrible for both men and women but for different reasons:

Research in Semester 2

In June 2012  Jon Millward, a self-proclaimed specialist writer published the results of a 4 month experiment called Cupid on Trial. He set up 10 dummy accounts, answered 25 questions the same, used similar sounding user names and wrote the same profile for all the accounts. The only differentiation was the photograph. For that he used 5 males and 5 females that 4 independent judges unanimously agreed on a ranking of attractiveness. He set this test up in 5 different cities in the States and 5 different cities in Britain. He then waited for unsolicited messages. After 4 months the results were stark. Two women had full in boxes (around 500 messages) and received 83% of all the messages. It only took 2 months for their inboxes to fill up so at that rate they could have received twice as many messages. All the women except one had more messages than the most popular man and 3 men sat within a margin of error.  Also interesting was that one in three men who viewed a profile sent a massage, while 1 in 10 women who viewed a profile did the same. While this experiment raises new questions (such as the content of the messages received), it clearly demonstrates that women will get bombarded with messages and they have no hope of filtering them, while males will send messages and can generally look forward to no response. In any case finding a match on a dating website (and OkCupid has a good reputation at least amongst the community of Hacker News) is something of a lottery.

Dating website experiments

Through out semester 1 my research consisted of a lot of reading, mostly non-academic but incredibly useful. In semester 2 I felt that along with reading, I had to be more hands on with my research. This would of course include the thought processes that I seem to have while making something - the mobile app - reading more academic material and experiments of my own. As the second semester started, I joined 3 dating websites. NZDating, FindSomeone and OKCupid. I was hesitant about this for a few reasons. One reason is that I’m not particularly interested in being on a dating website. The whole time I’ve worked on this project, I’ve had to battle with the suspicion that my end goal is to find dates of my own. This project has nothing to do with me, it started before BCT with certain financial motivations and a sense that I could do such a site better (by certain metrics). Then, when it became a project it became an interesting subject. Another reason that I was hesitant is that my own research told me that it could have a potentially negative emotional impact. Even as a researcher, I would be putting myself up on the site, my pictures, my description of me. If I send messages and one in ten get answered, it wont be a nice feeling no matter how detached I am from the process. Also, I didn’t intend to be completely cold - I was not planning on sending messages randomly, but to people that I might actually find something in common with. Last of all, visiting these sites turned up something interesting: I was being matched with friends and acquaintances. I did not particularly like the idea of being visible on a site to people that knew me, and could read my profile. I pushed on but did not send any messages for a while, until a classmate (while getting coffee with them funnily enough) told me that I need to “get amongst it”. So I did.


I was perhaps rather fortunate that the first person I chose to send a message to messaged me back (user name melonpop). We talked a little bit but in the interests of my mobile application that clearly puts focus on meeting people, I kept conversation to a minimum with the hopes of actually meeting the person. The “date”, 2 weeks later was terrible. It wasn’t a date, and in fact I discovered that I had crashed her friend’s “leaving for England” drinks at a sports bar. I had to deal with her incredibly annoying friends. Things also fizzled a little bit when there was the revelation that I was a student (this was clearly stated on my profile) while she expressed some sort of hostility towards higher education. We never met up again.

This left me slightly reflective about any form of online dating, even my own application that was different. However there were a few factors at play. One is that this person had no idea that while I was genuinely interested in meeting her, I was also just performing research for my project, which happens to function very differently from the dating website that I met her through. The basis of my application is meeting people for during small breaks in the day, coffee breaks for example, which is totally different from meeting someone at a bar on a Friday night. The meetings either way would ideally be conducted one on one, and this particular meeting was less than ideal in many ways. The setting cannot be blamed on the website, but the person who chose such a setting in the first place. None the less this single example dampened my enthusiasm for a couple of weeks. A few subsequent messages sent through NZDating were met with no reply and this along with the general seediness of the site itself pushed me further away from wanting my application to be a dating app. The 3 different sites that I joined had different vibes around them and produced different results.

There are other things that I picked up from NZDating. A lot of women end their profiles with statements along the lines of “I don’t want to see your [genitals]!!” or “if you are just after sex, then don’t message me!” A smaller number of women complain about couples contacting them or males continuing to bother them after they haven’t replied and essentially made it clear that they are not interested. I lament that I  haven’t read male profiles to see if there are similar patterns in complaints, though at the time it just seemed slightly weird for me to be checking out male profiles. All of this points to the bad behaviour and that it’s entirely permissible on NZDating. On one hand this makes the site open to all kinds of people, on the other it gives license to people prone to using that freedom to annoy other members. For that reason I imagine that it becomes exceedingly difficult for anybody relatively normal to start a normal conversation with anybody else relatively normal.

I did send more messages to people and would occasionally get responses. I asked one person (user name nix86) who in her profile had hinted that she has had some interesting encounters online on the site, what some of the most interesting messages she had received. I’m not terribly comfortable repeating her top three responses, they were quite extreme. She did however say “And keep in mind that these came from people with relationships profiles, and appeared relatively normal lol.”.


Findsomeone I should say I didn’t get much from because one cannot send messages without paying a monthly subscription fee which I was not willing to do for a number of reasons, quite separate from the study. I’m essentially opposed to financing their site. That said the quality of the experience is somewhat different to NZDating. NZDating feels like a wasteland, it’s like visiting a Las Vegas back road, or closer to home, K Road. Findsomeone by contrast has certain standards. People already in relationships are asked to not join. Pictures are vetted by real staff and the main picture must be a face picture with no sunglasses. The site promotes an image that gold members (those that pay) are actually serious about dating and I suspect that people do buy into that idea despite the unavoidable fact that this serves the site’s bottom line.


My experience with OKCupid was more positive. The site has a relatively functional design and used algorithms to match people based on questions and personality tests that a user could take (voluntary). This in some ways goes toward resolving the problem with shoehorning a person into a database. The design of the site made it feel like a nicer place to be. It seemed to promote a certain standard of interaction without constant intervention from site administrators. I mostly lurked on the site but eventually decided to be more active. I sent and received a few messages (which I made a point of always answering, though perhaps that’s because I’m not receiving an average of 50 messages a day) and inadvertently have made a few online friends/acquaintances, all of whom know that I’m working on a project related to dating websites and a mobile application. I have received some odd messages however. One from a person who claimed to be “looking for love”. In hindsight I probably shot this person down a little bit. I responded to that with “okay...” which was probably dripping with “are you for real?!”.

Development of project

I had started with the intention of creating a new dating website but there were 2 factors that came into play very early on Semester 1. One is that I also wanted to explore mobile application development, more specifically, native iOS development using Objective-C and the Cocoa Touch framework. The other was that I had considered the idea that using location awareness in a mobile phone was somehow appropriate for a dating application. These two ideas worked well together and as I examined the information I had about dating websites I realised it also tied in as a potential solution for many of the problems that my research had raised with dating websites in the first place. A consideration with mobile phones is that information has to be condensed and simplified into a suitable format for their small screens. This was a useful for a dating website because dating websites presented far too much irrelevant data in the hopes that it would make up for the fact that they cannot really capture the essence of a person, even with an algorithmic approach such as OKCupid. As Dan Ariely said (paraphrased), “people are more like wine, and you can’t describe wine with a database”.

Dating websites I had decided collected far too much irrelevant data on a person because that played to the strength of the technology used. But people are not a collection of statistics. I am not my height or weight or eye colour and I imagine that these are not the things that one remembers or even notices about me. I personally have certainly never become interested in a person from data that one could enter into a database about them. Dating websites encourage a user to interact with this data, perform searches on it and when they find someone, to sit behind the computer and talk to another user. This certainly has it’s merits, but it touches on a wider concept that a lot of social networking technology actually sits in between the user and interferes with the social. Dating websites on one hand enable people to meet other people but on the other hand go some way to preventing them from actually meeting. On one hand they enable interactions that probably would otherwise not happen, but on the other hand they shape those interactions unnaturally. By contrast my application didn’t collect much data on a person and it followed that one could not search for data that didn’t exist. The application was about real interaction. My hope was that my application would facilitate interactions between users and then get out of the way.

My experience with dating websites turned me off the idea of CoffeeDate being a seen as dating application. A strength I touted in Semester 1 that it was not a dating website so therefore didn’t have the same stigma associated with it. But this didn’t go far enough in semester 2. I have begun to question how relevant a user’s picture is in the application. Is this a relic of a dating website or does it serve a purpose beyond that of online dating? I personally believe that it does serve a purpose but it should not be a required element, so the application has evolved accordingly. The only information a user is required to enter is a user name, an email and a password. This simply makes their account functional. I will get back to this further on.

I went to Dev World in Melbourne in September. One talk in particular seemed relevant to my application and a general interest of mine. It was called “App UI Usability”.  A lot of what was spoken about already made sense, but there were a few things in the talk that made me re-evaluate the layout of the application. An example was to not crowd a screen with too many form elements. As a result I decided to investigate spreading  the registration from and options across more screens. In the talk it was discussed that users don’t generally like entering information into a mobile phone so forms should populate themselves as much as they possibly can with data that they get from elsewhere on the phone. This is more of a technical problem for me at the moment, though I intend to deal with it once other bugs and problems are fixed.

Another concept I considered but never really got to develop further was the gamification of my application. I wanted to make iterations of the application and find methods to turn meeting people into a game. The idea behind that was to make the app more fun for users and remove certain frustrations if it wasn’t really working out for people. An idea that I’m not entirely familiar with but I started to think about was that games are social and that they bring people together. This could possibly have been used to  further the intentions behind the application in a fun way. I did not develop this idea at all because actual application development consumed the time I needed to try this out.

More experiments

I set up an experiment where people in the BCT could sign up to have coffee with a random person that they have never spoken to who is also in the BCT. While there are certain flaws in the experiments, such as everyone in the degree at least has the degree in common, I wanted to find out what people made of the concept, and the people of BCT were the most available to me in the time frame that I had. Participants had to write their name on a slip of paper and one interesting thing about them as a conversation starter. This mirrored the “about me” box in the current iteration of the application. Incidentally there is a tight character limit in the “about me” box in the app. It’s meant to be sort of line a one liner to start conversation or be a signature of some sort. The slip of paper also had space to enter what year a participant was in so that when I matched up the names, I mixed people from different years up to ensure that they didn’t know each other. Otherwise the matching was random. They put this paper in a box and at certain times I’d take names out and pin them up in pairs. There was then another form that they were to fill out, asking them question about the experience. I was not entirely sure what I wanted to know specifically at this point but I thought some preliminary research might help me find that out. The questions were as follows:

  • What was the experience of having coffee with someone you (probably) don’t know like?
  • Would you do this again (have coffee with a random person)? 
  • Do you think you’d ever use a smart phone app whose sole purpose was to meet new people for a coffee break?
  • Describe what you were expecting before you entered in to this, was it different and how?
  • Do you think you might have made a new friend/acquaintance you might not have otherwise made? Why?
  • Anything else to add?

I posted about it a few times in the BCT Facebook group and on the white board at the entrance, pointing to the box and a small A4 poster that I had made. My concern was getting participation and this turned out to be well founded. While the idea seemed like a popular one but it wasn’t a particularly high priority for students concerned with getting their work done in the second half of the semester. This experiment might have fared a little bit better in the first half of the semester, had I considered it at that time. Around 16 people signed up, but only 2 pairs actually met up and had coffee, and only one of those pairs filled out the form. The second coffee date actually happened at a bar in front of a crowd of us celebrating the last day of Studio, and while it was interesting to watch, it was not really representative of the intention of the experiment or the application The feedback I received from the pair that did do the experiment properly was positive however. They enjoyed talking to someone new and both believed that an application facilitating such a thing had its place.

Another thing was happening around the time that the experiment was taking place. I was building the actual location awareness and table view of other users at the time (the registration and authentication parts took a disproportionate amount of time) and as mentioned I was also discovering how much I dislike dating websites, particularly NZDating. The experience was best described as seedy. I started wanting to distance myself and my application further away from a dating focus. I had already done this a little bit at the binning of semester 2. I removed sexual orientation from the application and I had been considering whether the preference of displaying males or females only was in line with an application that was not focused on dating, though I kept it in for the meantime, partially because I wanted solve it as a programming problem. As I mentioned, adding photos serves a purpose, but I have been considering what it’s removal would do to the application, and how one could adequately replace photos with something else. Being able to add photos in easily from a mobile web application has in fact only been possible with the advent of iOS6. Previously web applications have not had access to the Camera. I’m not yet certain about Android or other mobile operating systems, but there would need to be a way around it, and it would probably require a clunky work around such as having to set up certain parts of an account from a desktop web browser, though this could also work in one’s favour if the application was to become more complex after all.

In some ways I felt that I had come full circle in my Studio. I had spend about 5 weeks in the first semester floundering around with a project that would have something to do with social networking and meeting new people in a way that current social networking websites cannot. I had moved into dating websites because I had a side project and it seemed to be a lot more interesting to me and had some thing that I could actually get stuck into technically. Now I found myself building a mobile application focused solely on meeting people.

The name of the application has been a point of discussion and contention amongst tutors, peers and it is something I have personally thought about a lot. In Semester 1, I wanted to position the application as something that was about meeting people but surreptitiously giving a wink to it’s dating potential. This led to discussion about what the application was actually about. Was it an innocent way to meet people or was it a dating app? What kind of message was a I giving? Perhaps the message was too mixed for the app to find success. My feeling on the subject was that it’s dating potential is what would sell the app but the pretence of just meeting people is what would make it popular and useful. On reflection I think the imagery that I used was possibly too overt even for that positioning of the application. As I’ve moved away from targeting it as a dating application I have considered a name change. None of the names have been as satisfying as CoffeeDate, and after discussions with various people finding opinions and my own thoughts, I’ve decided that CoffeeDate is a generic term for meeting up with someone for coffee, and it’s dating connotations are only as strong as the imagery surrounding the words let it be. CoffeeDate has a nice ring to it, and it’s up to me to come up with good artwork and layout along with a good description of what the application is about.


I’ve been asked why coffee had to be part of the name. The short answer is that getting coffee with someone is a social thing. In the work place I’d occasionally find time to meet up with friends nearby for coffee and it was really just a catch up as well as a break where we got to drink coffee. The coffee and the social meet was a double shot pick-me-up before heading back to work. In the BCT it slowly became tradition amongst friends to go and get a coffee together. We’d usually go in pairs, and it was as much about getting some fresh air, spending some time together and discussing whatever was on our minds as it was about getting an actual coffee. It’s almost like a modern-day cigarette break in a few ways. It’s social. It’s a drug that picks you up and some would consider it a vice. It involves leaving the premises and getting outside. Last of all it can get expensive. It is rather a lot healthier though. The word date is used in Lunch Date and Dinner date. Using the modifier changes the meaning of the word from being about dating to being about a more innocent social or business meeting between friends, acquaintances, business partners, clients or even strangers. A Coffee Date is short and informal and simply means that 2 people are meeting at a certain time on a certain date.

I came across the name Sherry Turkle early in the year must have thought it was relevant to something for I discovered her name typed into my iPhone Notes application but I don’t remember when I did that. I heard her name again in a seminar on mobile technology in education, and some of her books sounded interesting. Her latest book “Alone Together” sounded like it was incredibly relevant to my work and my own personal interest in social technology, so I borrowed a copy of the book and have been reading it. A quote from early on in the book resonates with my own feeling on social networking, mobile technology and even dating websites and what it all has become:

These days, insecure in our relationships and anxious about intimacy, we look to technology for ways to be in relationships and protect ourselves from them at the same time

Social technology has a dark side, much of it seems like unintended side effects of a utopian vision where technology actually connects us and some of it perhaps as a result of our capitalist system and our consumerist bent. We’ve become more connected with each other through computer and mobile networks, our laptops and our smartphones and our tablets. We can keep in touch with more people from further away then ever before, and we can do so instantly. We can gain insights to each other’s current events and thoughts through status updates, photos, instant messages, email and gain context with technologies like geo-tagging. Despite all of this more and more people are acknowledging that the very technologies that connect us over their wireless networks are disconnecting us in the real world. Facebook can put one in reach of an old high school friend yet it also winds up replacing real meetings with closer friends because it’s more convenient. This is not a new phenomenon, but it’s prevalence has become more obvious with new technologies. Dating websites with their messaging systems lock many unwitting people into an endless message cycle. People are more comfortable replacing real life interactions with interactions that they can control in time, but at the cost of not actually connecting with people in real life. Text messaging keeps people at arms length, and we can control when and how we will respond and as a result are sometimes afraid of real conversation. We’re more connected but less connected. Text messages with their small character limit  also point to another phenomenon that is deeply related to our disengagement with real people. We are being more distracted. More and more people look to their smartphones for a new distraction. A new text message, email, Facebook message, status update, tweet and the list goes on. We’re unable to pay attention to one thing for long enough to be properly engaged. Our minds are always elsewhere. We can’t even have real conversations with people because we are busy checking our phones. We can’t read a book or even an article online without flicking to another tab for a new distraction. Social technology has given rise to a population with a low attention span and a certain anxiousness about being alone yet afraid of any kind of real intimacy.

It was my aim for this project to use technology where it is useful, to enable real life connections to be created, but then to step out of the way completely, rather than replace those interactions. It started out as an answer to traditional dating websites, but it has a place in a wider context. I wonder what the role of a dating website actually is, as it seems to leapfrog over the process of just meeting people and straight into meeting a partner. My feeling that the largest problem with dating websites was that it reduced people to figures that fit into a database completely skipping the substance of a person, and aiding a new kind of superficiality as people were searched upon by that criteria proves not to be to biggest problem with dating websites. Well, it is for the sites themselves, but the biggest problem by far is that dating websites promote the endgame. They want to short out the process of just talking to people, making friends, being social and the entire journey. Yet it’s the journey that is the fun part.