Big News: FounderDating is joining OneVest to build the largest community for entrepreneurs. Details here
Latest Notifications
You have no recent recommendations.
Name
Title
 
MiniBio
FOLLOW
Title
 Followers
FOLLOW TOPIC

Question goes here

1,300 Followers

  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur

Prototyping a Tech Product: What are the best practices from a technical/architectural standpoint?

Below are some variables I value when deciding how to create a prototype. Please add/respond/devalue. Thanks in advance for your feedback.

Functionality: Not perfect but works as intended
Deployment speed: I would want all the (inexpensive) tools that will make my deployment faster
Legal ramifications: If I go OSS, will it screw me up past prototype phase?
PAAS: Do I use one to save time, if so which and why?


6 Replies

Dan Abdinoor
1
0
Dan Abdinoor Entrepreneur
Go with what you know.

If you are not technical, I suggest you get someone on your team who is. A non-technical person is not going to make wise decisions on these topics. Further, when a technical person joins you they may not be in agreement on one or all of the decisions that were made before they joined.

If you are working with an outside technical firm, they should have expertise in some tech stack. That expertise allows them to focus on the goals of your product, and not the plumbing.
Brian Piercy
0
0
Brian Piercy Entrepreneur
(This may be more relevant to HW then SW, but still worth considering:) Any thought to having a limited rollout? To beta customers that are willing/able to provide substantive feedback?
Mohammad Forouzani
1
0
Mohammad Forouzani Entrepreneur
CEO at Forecast.net
I agree with Dan - dont try to pick the best X, or the most efficient Y - just use technologies you are most familiar with. The point of a prototype is to prove a concept or a business model, or maybe just assess interest. Dont waste time trying to pick the "best" things, only pick the things you are most familiar with and will get you to prototype launch as soon as possible.

Remember, if all goes well, you can rewrite the whole thing without too much effort, it is after all... just a prototype.
David Fierbaugh
0
0
David Fierbaugh Entrepreneur
Senior Mechanical Engineer at Microsoft
There's prototyping (roughly same form factor and technology as final product) and then there is doing a proof of concept. A proof of concept does not need to resemble the final product except for trying to show the functionality. It will typically use existing off the shelf components and software to speed development along. The things you learn in a proof of concept can GREATLY ease learning those same lessons after building a prototype. You may discover features that just don't add the value you expected, or are technologically difficult to include in the initial prototype; and you will likely discover features you hadn't thought of which greatly enhance the final product.
Luke Szyrmer
0
0
Luke Szyrmer Entrepreneur • Advisor
Forward-Thinking, Creative Software Product Manager and Author
Modularity's pretty important, in my opinion, as it's then easier to add/remove features as you get feedback. So for example in software, paying a lot of attention to interfaces and boundaries in the code makes it easy to swap in/out features.
Christopher Poletto, PhD
0
0
President at Restisense Corporation
This may be obvious, but I would just like to add that even getting a bid to build a prototype is considered public disclosure by US Patent law. Ensure that you get non-disclosure agreements to protect your intellectual property everytime you discuss the prototype with a new entity.

I agree about the modularity and hiring people who have done similar work before. There is a big difference in the approach to building a prototype than to building a production model. Skunkworks are better for the former.

Expect several iterations. You learn something each time. I am currently building prototypes for two clients. They are each in their third generation. The good news is that prototypes can be rapidly developed and may not take long between iterations, especially if you have multiple options and start ordering parts for all options from the beginning.

Join FounderDating to participate in the discussion
Nothing gets posted to LinkedIn and your information will not be shared.

Just a few more details please.

DO: Start a discussion, share a resource, or ask a question related to entrepreneurship.
DON'T: Post about prohibited topics such as recruiting, cofounder wanted, check out my product
or feedback on the FD site (you can send this to us directly info@founderdating.com).
See the Community Code of Conduct for more details.

Title

Give your question or discussion topic a great title, make it catchy and succinct.

Details

Make sure what you're about to say is specific and relevant - you'll get better responses.

Topics

Tag your discussion so you get more relevant responses.

Question goes here

1,300 Followers

  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
Know someone who should answer this question? Enter their email below
Stay current and follow these discussion topics?