I have an idea for an app that has a multi million dollar valuation if created. But I can't make it

[Ethnic Vagina Finder]

What's the app?

Its a dog bark translation app. You speak into the phone and it will translate into a series of barks that will communicate with your dog. I'm gonna call it the Rufferizor

Spoiler

 

[Mr. Manhattan]

Its a dog bark translation app. You speak into the phone and it will translate into a series of barks that will communicate with your dog. I'm gonna call it the Rufferizor

 

[LA Fisher]

 

[newarkhiphop]

Its a dog bark translation app. You speak into the phone and it will translate into a series of barks that will communicate with your dog. I'm gonna call it the Rufferizor

will it support multiple languages?

 

[Juliano Soprano]

Well first off The Winklevoss's still made out with a pretty hefty sum. So if someone sharked your idea, you'd still make a decent amount.

Secondly. multi-million dollar evaluation? and the thing hasn't even been created stop it, you don't know this.

And last you're worrying about the wrong thing, hire someone to build it for you, make them sign ndas/noncompete or whatever and keep it moving. You're not at the stage to be worrying about someone sharking your idea. All you're doing is making excuses for yourself to not be taking a risk

Its a dog bark translation app. You speak into the phone and it will translate into a series of barks that will communicate with your dog. I'm gonna call it the Rufferizor

This thread legit got me

@Ethnic Vagina Finder even though I know you playing about that idea, people legit ask programmers to create complex weirdo shyt like this, that's why it's so

 

[Ethnic Vagina Finder]

will it support multiple languages?

 

[klientel]

I guarantee the app already exists.....

There isn't anything left to create in this current gen that is truly going to be NEW

 

[newarkhiphop]

http://www.gmanetwork.com/news/stor...ogy/woof-dog-to-human-translator-in-the-works

Soon you may no longer have to wonder what your dog's barking means: a device is in the works to translate the canine's thoughts into English.

Dubbed "No More Woof," the device uses electroencephalogram (EEG) technology to read the dog's thought patterns and read them out in human language.

"Among the patterns we have found are 'I'm Tired,' 'I'm excited' and possibly 'I'm Hungry' and the clearly intense brain activity when a dog sees a new face, that we translate into: 'Who ARE you?'" the developers said on their Indiegogo page.

They said they set a low $10,000 goal to be "the start of future development."

People who preorder the device will get the first edition of the product, while showing support for further research "into finally breaking the language barrier between animals and humans."

According to the developers, the device also uses special brain-computer interface (BCI) software.

They also said that since animal brains are less complex than humans, their signal patterns are more distinct for feelings of anger, curiosity or tiredness.

sorry breh already exist

 

[Mr. Somebody]

Don't know how to make apps. And Im pretty certain it doesn't exist.

How do I go about protecting my idea and hire someone to make it without getting Zuckerberged.

Friend, there are people who make apps for contract fees. All you have to do is pay them to make it and sign paperwork that they will not steal your idea, give it to someone else or profit from it in any shape or form outside of your compensation. NOw, if you decide after you become a multimillionare to pay them a bonus, thats up to you, friend.

 

[Malik]

I don't necessarily agree with this. The amount of time it'd take for him to learn program and then build it himself would be so long that the window for the idea to even be viable may have passed. Or someone else may come up with the idea and beat him to the punch. Idk how much it costs to build an app, Im sure it's in the mid 4-figures range. But Im sure he can come up with that money. Think about all the stuff you spend money on and cut back and put the money to your idea. Especially if you truly believe it's worth millions.

To get a good programmer to build a website/mobile app for you.....and I'm assuming he's talking about an Instagram/Snap Chat/Four Square/Tinder type project....which is very large.....then yea....a good programmer is going to want $7,000-$15,000 to build it. And I'm seriously lowballing it here. Because I've seen quotes for higher. Trust me bruh. I speak from experience.

 

[L&HH]

To get a good programmer to build a website/mobile app for you.....and I'm assuming he's talking about an Instagram/Snap Chat/Four Square/Tinder type project....which is very large.....then yea....a good programmer is going to want $7,000-$15,000 to build it. And I'm seriously lowballing it here. Because I've seen quotes for higher. Trust me bruh. I speak from experience.

Yea I was thinking between 5k-8k. But yeah I knew it wouldn't be cheap, I mean if you break down the amount of time it will take for him to learn the coding and give it a /hr dollar value it might come out to be $8k anyways. But again if you really believe in your idea then that should be worth it imo.

 

[Malik]

I hear this shyt about 10 times a week.

Person: "I have an idea for an app, can you code it for me? We can share the profits."

Me: *already disgusted by the fact that this person thinks my time is so unimportant as to labor for weeks on his idea* What is it?

Now comes the funny part. It's always one of these scenarios: Something very simple and already over-saturated idea OR something extremely difficult to accomplish with one person on limited time. Never in-between.

Person: "What about an app that uses the front camera as a mirror?"

OR

Person: "What about an app that uses the camera to scan hair follicles and then run an algorithm to analyze the diseases in someone's body from data taken from the analyzing? Then we can cross reference it on a worldwide database we will create. Can you do this yourself?"

I don't necessarily agree with this. The amount of time it'd take for him to learn program and then build it himself would be so long that the window for the idea to even be viable may have passed. Or someone else may come up with the idea and beat him to the punch. Idk how much it costs to build an app, Im sure it's in the mid 4-figures range. But Im sure he can come up with that money. Think about all the stuff you spend money on and cut back and put the money to your idea. Especially if you truly believe it's worth millions.

Unless you have deep pockets ($8,000-$20,000 laying around), you're better off teaching yourself how to code and doing it yourself. Good programmers are like beautiful women. They know they're in demand. They're not gonna develop your shytty app and waste their precious time, when they can be getting paid for a project or building something cool for themselves.

@L&HH There's your answer...I know how coders talk

Here's an example. The guys who started Yipit ran into the same problems. Had no real money to hire programmers and couldn't attract a technical cofounder. So one of the guys taught himself to code over a year, and they built it themselves.

http://yipit.com/
http://viniciusvacanti.com/2010/11/01/6-things-you-need-to-learn-to-build-your-own-prototype/

I remember reading the Learning Python book and putting it down after 20 pages and having a major freak-out.

What was I doing? I had been out of college for 5 years having learned a ton of finance and I was reading a book called “Learning Python” with a mouse on it?! Did I just hit a huge reset button on my life? Was I even going to successfully learn all of this? Did I even know everything I was supposed to learn?

I didn’t have the benefit of reading the post below. No one told me it was possible nor that I should do it.

But, we were going to have to give up unless I became our technical co-founder and I was definitely not giving up. So, I kept reading the Python book.

Six months later, much to my surprise (though I now know why), I was ready to build any prototype we needed. That made us very dangerous and credible as a startup team. I still do some development for our team and, more importantly, I have a much better sense of what is possible and how long things will take making me a much better founder.

Lastly, you’ll get a lot of skeptical looks from people when you tell them you are trying to teach yourself. Just remember that they’re not in the arena, you are.

 

[L&HH]

@L&HH There's your answer...I know how coders talk

Here's an example. The guys who started Yipit ran into the same problems. Had no real money to hire programmers and couldn't attract a technical cofounder. So one of the guys taught himself to code over a year, and they built it themselves.

http://yipit.com/
http://viniciusvacanti.com/2010/11/01/6-things-you-need-to-learn-to-build-your-own-prototype/

Yea, Im aware. I know people just like the op, they come up with these "great ideas" (really aren't that great) and they put all these barriers on themselves as to why they can't do it. What if someone steals my idea, I can't code, what if it's not that great idea, etc. Im just trying to give the most simple solution.

It probbaly was best for those yipit guys to just code it on their own but it took them a year of learning to code to do it. Im sure between them, they could have possibly raised the money to do in less than half the time.

 

[Malik]

We Were Screwed

As the summer of 2007 came to an end, I had one of the most depressing and humbling weeks of my life. Just a few months before that, I had left an office facing Park Avenue making an absurd amount of money for a 26 year-old to start an internet-based company. I was now sitting in my apartment realizing, for the first time (and not the last), that I had absolutely no idea what I was doing.

We had been working on a site to help people share links with each other in private groups and had been using an outsourcer to build the first version. We wanted to do something in local but thought this site would be an easy way to quickly test our relationship with the outsourcer and get our feet wet.

After handing them an 80-page product spec months earlier, we were able to finally test the site five weeks later than scheduled– so much for quickly testing our relationship. Nothing worked. In fact, you couldn’t even share a link. As depressing as that was, it was made worse by the fact that the outsourcer told us he had tested out the site and “found no bugs.” I remember reading the email and then looking over at the other tab I had open with 16-pages of bugs we had found in 4 hours of testing. We were screwed.

While we continued to work with the outsourcer for a month and a half, we knew it wasn’t going to work in the long run. It wasn’t even really the outsourcer’s fault, it was our fault. We definitely weren’t managing them well. But, more importantly, we didn’t know what we were doing as entrepreneurs. I started reading Steve Blankand Eric Reis and realized we were going to have to do ton of iterating and having an outsourcer in the middle was going to make it really hard to be successful. We needed to iterate quickly and, thus, we needed someone on the team to do the iterating.

So, it was now October and, after failing to find a good technical co-founder, we knew we had to make a decision. Either we give up or one of us would become our technical co-founder. Since I had taken two intro CS courses in college, we decided I would become the technical co-founderand Jim would help out on the front-end development (HTML/CSS) side.

I was terrified. I had never built a site and hadn’t written a line of code since my freshman year of college (7 years ago). I thought we were doomed.

But, to my complete surprise, six months later, I was able to build almost any prototype we wanted. Really.

Why You Can Become Your Own Technical Co-Founder
It turned out that it was a lot easier than I had expected. At least it became easier when I realized that the goal wasn’t for me to become Yipit’s CTO. My goal was to build a prototype that got traction. (By traction, I mean that visitors convert into users of your site, those users come back to the site and they refer their friends) Once we got traction, we had investors and great technical co-founders knocking on our door.

Another way to think about it is that you’re just going to be a temporary technical co-founder. You just have to know enough to build and iterate on a prototype to get traction.

Here’s what I found that makes it much easier than you would expect:

• Minimum Viable Product (MVP). To get traction, you don’t have to build a complete product. You just have to build some small, core aspect of your idea and get people to start using that. That means you can get something out much smaller, get traction and then bring in a real CTO to help you expand the product. The version of Yipit that got us traction was built in 4 days. It took us a year of customer learning to know what to build. But, from a technical perspective, the MVP that got us traction took us just 4 days.
• Don’t have to worry about scaling and security. Scaling and security are really complicated technical challenges that you don’t have to actually worry about (this assumes you aren’t working on a project where scaling or security are a core aspect of the business). Getting traction doesn’t involve signing-up 1 million users. By the time you run into scaling issues, you’ll have an awesome CTO to help you fix it.
• Doesn’t have to be perfect. I used to worry that my code had to be perfect. Guess what? It’s going to get thrown away and re-built by your future CTO. It doesn’t have to be perfect or pretty, it just has to work. I remember playing with an early version of Foursquare and getting MySQL errors. It didn’t matter because they now have an awesome tech team that re-built it all.
• User interface and experience is more important. You’re not going to be working on your own complex sorting algorithms or MapReduce. Most web startups are CRUD apps. The technology is simple in the back-end, the value created is primarily in the user interface and user experience. UI / UX is a real challenge, just not a technical one.
• Django and Ruby on Rails. There are amazing advanced web frameworks out there that make building a website much easier. A lot of the stuff that would have been a nightmare 8 years ago is trivial now.
• Community help. Whenever you run into bugs / issues when developing, do a google search for the bug and you’ll find someone has already posted it and someone answered it. With StackOverflow, that’s gotten even better.
• Systems Administration help. Setting up your server, dev environment and production environment can be really frustrating and tedious. But, you can hire someone who has already done it and have them set it up for you in less than 10 hours. That’s what I did a year and half ago and that person became our awesome CTO.
• Open source apps. It turns out that pretty much everything you are trying to do on your web app has already been done by someone else. Want to integrate with bitly, someone built that library client. Want to add comments to your site, someone’s built that plug-in. Best of all, they are all free and open source. Worried you’ll pick the wrong one? Who cares. As long as it works, move on. You can always change it later.

I hope this list gives you some confidence that becoming your own temporary technical co-founder is not as hard as it may seem. Of all the reasons I gave above, the most important one is to remember that you just have to hack something together that works. Once it works, get people using it and keep hacking till you get traction. It doesn’t have to be perfect, scalable or secure. It just has to work.

 

[L&HH]

Thanks, I might have to re-evaluate my stance on this