Does one “make an app” or “build an app”? Of course, there are oth
Does one “make an app” or “build an app”? Of course, there are other alternatives. One could also “develop” or “create” an app. Although an outsider to programming, i understand there is no one way to describe what one does when their work involves (web) applications. But, for example, one can’t say that they “do an app.” There are certain ways you can describe this activity that involves coding and programming and leads to the development of an app. But one among the persisting ways of verbalizing this activity, is “to build and app.” Apps and websites are simply and quite commonly refered to as “built” things. This is what interests me, this relation between coding (think language) and building. It interests me (as an architect who looks for inspiration in language, say, as built form) because it draws attention to this elusive relation between “writing” (think code) and “building.” Programmers write code. Through it, (i.e. their knowledge of this language) they build things (like websites and applications) Academics write too. They don’t exactly “build theses” (they build arguments, heck they do build theses!), but their writings “rely on” evidence as “support,” they are expected to be “structured,” and to lead to a product, say a book. Programmers, on the other hand, they also write, and their work too relies on structure, and it too leads to a product, say an app. Architects aren’t commonly refered to as ones who “write.” They are thought of as ones who “draw,” “design,” and “build.” Their work, almost too literally, also relies on foundational supports and structure, and it too leads to a product, namely, a building. There is a tertiary relation here between coding, writing and building that needs to be unpacked.(screenshots are results of googling “make an app” and “build an app”) -- source link