App prototypes, what do they mean?

#1

Post by capex » Fri, Jun 29, 2012, 12:45 PM UTC

I can't find an answer to this by googling.

When we talk about app prototypes, do we mean a fully functional application including databases and all functionality of the app? Or do we just mean the visual UI interacting through buttons etc but without any backend functionality to support it?

Re: App prototypes, what do they mean?

#2

Post by gyardley » Fri, Jun 29, 2012, 1:33 PM UTC

The answer varies depending on who's talking - ask for clarification from the specific people you happen to be dealing with.

Re: App prototypes, what do they mean?

#3

Post by antm » Fri, Jun 29, 2012, 1:40 PM UTC

Ultimately a prototype is just a tool for learning and discovery. So what you build depends on what you're trying to learn or work out. I've built prototypes as powerpoint decks, basic HTML/CSS, and as apps built in Rails or PHP. Sometimes with a database backend - or with some spoof of one.

Re: App prototypes, what do they mean?

#4

Post by yashchandra » Fri, Jun 29, 2012, 1:45 PM UTC

Short answer: It depends.

Long answer: In my experience, prototype is used very loosely and can mean many things. But the point is that a prototype is not a fully functioning app/system/software yet. It is used to demonstrate the possible features/functionalities that the app would/could have. How you demontrate it depends on the specific case. Some prototypes can be created using a simple word/powerpoint slide, some can be created using mockup screens/wireframes and some are semi-functioning products. I do not think there is one single answer to this.

Re: App prototypes, what do they mean?

#5

Post by capex » Fri, Jun 29, 2012, 2:53 PM UTC

In the context of the average web app then, a html/css prototype (which can later be used in the project) would be a decent prototype. As long as they convey what the requirements of the project are.