CampCite started with a very simple pitch, "Remember those old projections your teachers used to…
When we took on the task of creating an events discovery platform, we knew we had something large ahead of us. The idea did not lend itself easily to our minimum-viable-product first approach, as the ideas kept coming in far faster than we could develop them.
But dedication to a methodology paid off, and as the platform unfolded, we received significant positive feedback on our branding, software, and services.
The branding in particular was something that many people thought crazy at first. In a swarm of blue and green corporate logos, nobody expected our pink to be anything other than a sore thumb. But those doubts were laid to rest as we released the first of our promotional products, including laptop covers, phone cases, and business cards. The logo jumped off of any surface it was placed against, and drew prolonged attention from even a casual glance. We’re proud of our branding abilities, and it shows in every project we undertake.
The interface design came next. We wanted to know how people interacted with events, how they created events, and what steps we could take to minimize the event creation process. We went through seventeen versions of the event creation process before we landed on our “working final” platform, which incorporated numerous programatic autofills, geography APIs, and simple language calendars to create what we believed to be the simplest process we could offer, with all the power and none of the hassle of other, clumsier setups. We limited our event discovery platform to a geographic and high-level categorization oriented approach, which coupled the usual “near me” discovery approach with user-oriented categorizations of events that we created after interviewing numerous event platform users to determine the actual way they wanted to find events-the result was a little less corporate, and a lot more human.
When we decided to deploy our API backend, we chose a very lightweight, extensible MEAN stack run on an Amazon AWS instance, with files handled via Amazon S3. Our system ran extremely quickly, and while we were still working on refining this portion at the time when the project was cancelled, we felt we were well on our way to bringing to life a competitive, user friendly product.
You can see EventsByMe in action here. If this resource is not responding, please let us know!