Member-only story
The Greenfield Paradox: Why Is Building a New App So Easy and Also So Hard?
Writing a new app from scratch is easy, right? Figure out how to stop building, go to market, and start enhancing
Any developer who has done greenfield development will tell you it’s the best way to write code. No existing system to maintain, no antiquated patterns or languages you have to deal with, and no constraints (within reason). Greenfield development is an easy, unobtrusive way to code, but at the same time, it is incredibly difficult to scope and deliver.
In case you are unfamiliar with the term, greenfield development simply means building something new from scratch. You are uninhibited by legacy systems and have nothing but possibilities in front of you.
If developers had their way, we’d likely never see a new piece of software again. Their tendency is to continue adding features until the product is “done.” Spoiler alert: Software is never done.
So how do you pare down your feature set and get your app in the hands of customers in the quickest way possible?
There are three things you must have before pushing your application to production.
1. Security
Security means a lot of things to a lot of people. When it comes to getting a greenfield product out the door, it really means one thing: Prevent your data from being publicly accessible.
Take the time to lock down your databases and data storage mechanisms. The last thing you want is a Capital One situation that compromises your whole operation. If you require a login to your app, make sure it’s secure. There are standards out there like Auth0 that provide easy mechanisms to keep your site safe.
The most important thing you can do is give your users the confidence that their data and information is safe.
If you use cloud services like AWS, they provide fast and easy ways to secure your databases and data storage. Through IAM, you can swiftly prevent an open…
