"I was inspired to build Nightingale after seeing a lack of full-fledged REST API clients on the Microsoft Store. Additionally, I realized that while other clients were incredibly powerful, they used nearly 500MB of memory even when performing simple HTTP request tasks. Thus, Nightingale was created. It is the first full-fledged UWP REST API client capable of sending RESTful HTTP requests and displaying the resulting JSON output. It also has a Collection Runner mode whereby you can submit groups of requests repeatedly to test your API. A premium feature includes synchronization of your workspace across devices. I built it over the last 4 months after spending a month designing it on paper. I decided to use UWP due to my experience with the platform, and I wanted to take advantage of the built-in performance and fluent design controls. It took some time to design and develop the synchronization stack. However, after several different approaches, I arrived at a solution that use an Azure backend service to handle the synchronization. I am proud of Nightingale's clean, fluent UI. And more importantly, I'm proud of its memory usage. The highest RAM usage I've recorded was 100 MB. Other clients tend to use more than 200 MB. Lastly, I'm proud of the UX for the Collection Runner. Being able to open multiple instance of the runner has led to new ways to test APIs. I learned that the UWP is capable of more serious apps. In the past, I regarded it as a "mobile-friendly" platform with little business as a desktop platform. This project has proven me wrong. My next goal for Nightingale is to add end to end encryption, polish the UI/UX a little bit more, and then prepare for the v1.0 release."