Why I'm Building Hold An Event
I created Hold An Event because all the other event registration web applications are not accessible to those using assistive technologies, like screen readers (JAWS, NVDA, Window Eyes, etc.), along with voice recognition software (Dragon Naturally Speaking). They are also difficult to use even on smartphones let alone an lesser phones. I found this out while running my first Accessibility Camp DC back in October of 2009 and then with our follow-up monthly event, Accessibility DC. People would show up without registering because they deemed the service I had chosen not to be accessible, even though these people would be considered by most to be power assistive technology users.
After the first Accessibility Camp DC and a few monthly meetings, I started looking into event registration systems and everything I found was inaccessible in one form or other. I mostly looked at all the larger ones is all. So over the last two and a half plus years, when I have had five minutes here or a half hour there, at coffee shops, on the train, or wherever, I put notes into my iPhone about creating a web-based event registration application. At first, I used the iPhone's built-in notes application, until a few people suggested I use Simple Note. This was because it had an iPhone application, along with a web application. By gathering all the different pieces of information you would need to create and run events over time, I had the time to really think about the roles/personas needed for an event.
The type of people I came up with could be people putting on the event, the attendees, paid attendees if that applies, sponsors, speakers, and even event staff. These roles work if you are holding a simple birthday party, the monthly book club, a tech event, or even a large conference. So we are talking a great amount of information, and I really had to think this through.
At times, I was like this is way too much work for just one person or I had other things to do and would do nothing about it for weeks or even months. No matter how hard I tried, the problem never seemed to go away and kept coming back to me. So after reading a lot of books, articles, etc. about start-ups, web applications, usability, and the like, as most would say I just needed to start and see where it would go.
When I Started
So over the summer of 2011, I finally started building the prototype to make sure I had the correct process, flow, and usability of the web application down before really starting the difficult work of making this a true working application. I even started with the mind-set of Mobile First (great book), which some are great ideas from Luke W. and others. My guess was that if I started coding the web application using web standards and accessibility in mind from the start, and if a person could do everything they needed to on their phone, then it should work wonderfully in a browser or on a tablet.
I started out simple and built a few of the needed input forms, which got me playing with responsive design and media queries. I made a concerted effort to get those few main screens right before building out a ton of pages. Once I got most of that complete, I moved on to the next set of forms.
My goal was to have the ability to make Hold An Event's web application to seem like it was processing real information such as a search for events, to registering for an event, etc. This was done by passing parameters in the URL to tell each page what static content to place on the page. This idea seems to be working fairly well, since when showing friends lately what Hold An Event looked and acted like, they asked what kind of database, etc. I'm using. I would then explained what I had done to make it a look like a fully-functional application.
By the middle of October 2001, I had a bunch of pages that worked well enough to start showing people at that month's Accessibility DC event and then more people at my annual Accessibility Camp DC event. Once those events were over, I didn't do any more coding until New Year's Eve 2011, sitting at my parents kitchen table coding from like 11 PM to 1:30 AM, because everyone else in the house more or less had gone to bed by 10:30 PM. Since then, I have been doing something to improve the Hold An Event web application just about every night and on the weekends too. Sometimes it was a little tweak here or there; other times it's been to add a new page.
At one point, I added a few different smaller non geek/tech events to be able to show people different types of events types and how the process worked. I also had to add in some code to display the different navigation paths people used, depending on what type of user they were. For example, is the person running the event or attending the event, which are the two types I'm worrying about now.
How You Can Help
The next step is to let people play with Hold An Event themselves instead of me demoing it on my iPhone, which means making it look and act better on a tablet or in a computer browser. Currently it's not the prettiest thing in a web browser, but it will do as a prototype.
Other big tickets items I'm going to have to think about are the security of peoples' information like name and e-mail address to start, along with taking money, once I get to that point, which is far off in the future. I'm only working on this a few hours some nights after work and then 6 hours max on the weekends, for a total of 10 to 15 hours a week.
So here's to making more progress over the next few months.
Where to find the Hold An Event Prototype
For those wanting to look at the current prototype, start by using the “tab” key on the Hold An Event's home page, doing so will let you find the link to the demo/prototype web application. Remember this “prototype will not save” anything you place in it at all. So please don't try and create an event to invite people to it and think it will work because it won't. Once you're there, use the search box to find events in “DC”, which will currently give you a list of nine events to view.
If you want to sign in to see the process of creating and viewing current events you're running, your past events, or ones you're attending, all you need to do is make sure you place at least one character in the e-mail address and password fields. It doesn't matter what they are, just as long as there is something there.
P.S. Have fun and please send me feedback about what needs to be done, improved, etc. I'm a big guy and can take the the bad with the good. I'm mostly looking for ways to improve things.