I started coding an app back when I was still in high school called "Closures."
It just got a huge overhaul.
I have 27,000+ lines of new code written over the last couple months on my downtime for the Closures app I’ve been working on. I’ve re-coded it from the ground up. For those who don’t know, in high school I made a closings and delays app that sources information and data from the local news station and parsed it in a way that categorizes it based on their status and organization type; School, Business, etc. I’ve changed it over the last few years to try to make it more exciting and easier to view and to understand what’s closed or delayed without needing to watch a news ticker or listen to the radio to know what the status of organizations are when the weather is horrible.
The most important thing to note for those who have used Closures in the past is that the web app has moved to a new home on the internet. I found it was better suited to have this project live on the domain closures.app rather than closures.co. The former domain will redirect users to the new location starting December 1st, 2018. If you've bookmarked or have saved to the homepage on an iOS device, please take a moment to re-bookmark it. I promise this is now the app's permanent home.
Over the last two years, I’ve pushed hard to develop an iOS version of the app. I ended up with a few different versions that were cool, but ultimately didn’t meet my standard of quality enough for me to support a release to the App Store. I’ve failed to continue this idea with the same excitement as I had when I had started.
The biggest thing I lacked was a powerful API. A core service that provided the parsed data to serve any platform regardless of any limitations. At the time, the API I had made didn’t serve the purpose I needed.
Over these last few months, I’ve built an API that not only serves real-time closings and delays, but also the weather including a comprehensive look into the 7-day forecast as well as some in-depth location information.
At this time, Closures API is private and not available for public use.
To expand on this, I’m excited to announce that I’m expanding it outside of Watertown and our surrounding areas. I’ve been able to take the idea of sourcing my local news channel station for closings and delays and have successfully been able to include several other news stations by tagging their data as well. I’m able to do this by cross-referencing zip codes from within 30 miles of that particular news station to a database of over the 42,000 zip codes within the United States to find the city and state where a particular organization has a closing or delay.
Prior to this, Watertown and surrounding areas in the north country were the only locations with exclusive access to Closures.
Now, over 400 cities and towns have access to Closures in New York, Virginia, Wisconsin, Illinois, Missouri, Minnesota, Ohio, Michigan, and Kansas. Over the next few months, I’ll be expanding this even further.
8 months ago - #apps