Sitemap
Potato Engineer

Potato Engineer

The original potato developer

From Developer to Prototype

2 min readOct 20, 2019

--

I have been working as a Software Engineer, writing production applications that scale in the cloud environments. Implementing applications that are production-ready is no easy task. However; Now I face new challenge writing applications that are only high fidelity prototypes. High fidelity prototypes are applications that have some level of functionality to them, but the majority of the app is fake (i.e. an application that looks production, but the only thing that works is the red button).

The new workflow in fast prototypes

Most of our prototypes leverage react-native. React Native is a cross-platform framework that can create iOS and Android applications developed by Facebook. One of the reasons that react-native makes perfect for prototyping, it is super simple to deliver a good looking and fast product.

Get Potato Engineer’s stories in your inbox

Join Medium for free to get updates from this writer.

Why a mobile application? A mobile application allows us to demo features to customers quickly and provide a way for the customer to do usability testing. When one is creating a prototype the key is to make the core features work efficiently and forget about the less important functionality( make it look good). As a developer, writing these types of applications reduces the overhead of 100% structure in the app and allows us to focus on making desired features alluring.

Consequences of Making a prototype application

As a Software Engineer, solving unique problems interesting ways is what makes the job worth it. Once it’s solved and moving to the next set of problems to build a solid product. Writing good software takes learning new skills contently, which take years to cultivate.

Writing high-fidelity prototypes takes that knowledge and throws it out the window. Prototypes require a new set of skill sets that might take time to learn but do not require the overhead of a normal application. These skills of prototyping are a little less appealing in the long run because it can make engineers comfortable at a faster rate in a market that changes every day.

Should you take on the mantel

Prototyping is good if you like a fast-paced environment, solve unique problems, and coding is not a high priority. The problems that are solved will disrupt the market of the core business, but will not improve the development skills of the engineer that will be marketable to other software companies that require in-depth knowledge of building actual applications. From my point of view, prototype applications are good as a side project. However, there is nothing better than building 12 Factor apps. Which do you prefer?

--

--