Loading...
Answers
MenuI have several startup ideas. How do I decide on my technology stack?
I'm a tech guy but I don't know much about mobile and web technologies. There are so many technologies and more coming out every day - Mongo, Cassandra, SQL, NoSQL. How do I decide on my technology stack? I'd like help to build my architecture. Thanks!
Answers
You need to be able to get feedback on your product as quickly as possible, so my advice is to choose the technology stack that will allow you to build a prototype efficiently. There's no right answer here: for some people it's LAMP, for others it's node, for others it's a Windows stack.
Worrying about the technology at the stage you're at is a red herring: worry about the product, the problem it solves and the user experience of your solution, and get feedback you can iterate on as quickly as possible.
I'm a serial startup CTO who's now a startup founder and CEO. Let me know if I can help.
Hi there!
Your choice of technology stack will highly depend on your objectives and projects. There is no one correct answer to this. It would be really great if you can share with us what kind of applications or projects you are working on in order to give you a proper advice. Thanks!
Tech stack always comes down to a combination of two thing: requirements for what you are trying to build and background/preferences for your team. There is no one generic set of answers you will get here because so much of your decision comes down to the specifics of these two factors. I strongly suggest you solicit feedback from friends and advisors that can learn more about your situation.
Like others have said, it truly depends on what your project's goals are.
That said, there's going to likely be many viable options when it comes to the tech and after you've narrowed it down you'll have other factors to consider.
For example; how many developers are out there that use said technology? are they cheaper to hire compared to developers who might use a different technology?
How can one technology (be it a database or hosting provider) lower your overhead? Or how and when does it increase? How does that impact your margins?
Obviously there's a LOT to consider. Just know that the considerations go much farther than just, "what's the best language" or "what's the best database" ... Performance and popularity are not the only things to consider.
I did want to put together a site that would help people decide based on project requirements and explain trade offs. It's going to take a bit of time (so many options), but this is what I help people with all the time on Clarity.
What technologies do you know? or are you outsourcing the development?
If you are worried about software costs for Microsoft there is a Startup Bizspark program where software is free.
Using Opensource is also great, there are so many options. Don't think you could go wrong with LAMP and server hosting end up being cost effective as well.
PHP and MySQL are powerful.
You are the lead developer/CTO of a new and shiny Start-up. It seems that on the product side of things you know pretty well where you are headed. The next stage of course is to choose the right start-up tech stack to implement the idea and make the product “come to life”. In addition, if you have a lot of runway you can choose a technology that takes more time to develop in the short run but has stability, scalability, and maintenance benefits in the long run. For instance, if you have a lot of runway you might choose a compiled language which adds an overhead of compiling the whole thing before you run your code to test if it works . A little known at the time functional language and VM. In addition, it will be easier to hire a software architect and/or developers for your team. If you are not an expert on the tech stack you intend to choose, it is always helpful to have commercial support to assist you. Choosing the right start-up tech stack can have a crucial impact on the success of your start-up.
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
Related Questions
-
What tools to use for mobile Prototyping ?
My 2 favourite are: - www.uxpin.com - www.flinto.com Flinto is by far my favorite for mobile. I also us www.balsamiq.com for anything wireframe. Sometimes I jump into Sketch http://www.bohemiancoding.com/sketch/ for more high fidelity mockups using their Mirror feature http://www.bohemiancoding.com/sketch/mirror/ Hope that helps. P.S. There's a tonne of Mobile UX experts on Clarity, many $1/min - call them, you'll learn so much. my2cents.Dan MartellDM
-
Whats are some ways to beta test an iOS app?
Apple will allow a developer to register 100 UDID devices per 12 month cycle to test via TestFlight or HockeyApp. Having started with TestFlight, I would really encourage you NOT to use it, and go directly to HockeyApp. HockeyApp is a much better product. There is also enterprise distribution which allows you far more UDID's but whether you qualify for enterprise distribution is difficult to say. As part of your testing, I'd encourage to explicitly ask your testers to only register one device. One of the things we experienced was some testers registering 3 devices but only used one, essentially wasting those UDID's where we could have given to other testers. Who you invite to be a tester should be selective as well. I think you should have no more than 10 non-user users. These people should be people who have either built successful mobile apps or who are just such huge consumers of similar mobile apps to what you're building, that they can give you great product feedback even though they aren't your user. Specifically, they can help point out non obvious UI problems and better ways to implement particular features. The rest of your users should be highly qualified as actually wanting what you're building. If they can't articulate why they should be the first to use what you're building, they are likely the wrong tester. The more you can do to make them "beg" to be a tester, the higher the sign that the feedback you're getting from them can be considered "high-signal." In a limited beta test, you're really looking to understand the biggest UX pain-points. For example, are people not registering and providing you the additional permissions you are requiring? Are they not completing an action that could trigger virality? How far are they getting in their first user session? How much time are they spending per user session? Obviously, you'll be doing your fair share of bug squashing, but the core of it is around improving the core flows to minimize friction as much as possible. Lastly, keep in mind that even with highly motivated users, their attention spans and patience for early builds is limited, so make sure that each of your builds really make significant improvements. Happy to talk through any of this and more about mobile app testing.Tom WilliamsTW
-
iOS App: Beta vs Launch Quietly?
I would suggest launching in a foreign app store only (ex: Canada). That will allow you to get more organic users to continue iterating without a big push. I got this idea from Matt Brezina (Founder of Sincerely, previously Xobni) https://clarity.fm/brezina - he's the man when it comes to testing & iterating mobile apps.Dan MartellDM
-
Pre-seed / seed funding for a community app... valuation and how much to take from investors?
To answer your questions: 1) Mobile companies at your stage usually raise angel funding at a valuation equivalent of $5,000,000 for US based companies and $4,000,000 to $4,500,000 for Canadian companies. 2) The valuation is a function of how much you raise against that valuation. For instance, selling $50,000 at $5,000,000 means you are selling debt that will convert into shares equal to roughly 1% of your company. 3) I would encourage you to check out my other answers that I've recently written that talk in detail about what to raise and when to raise. Given that you've now launched and your launch is "quiet", most seed investors are going to want to see substantial traction before investing. It's best for you to raise this money on a convertible note instead of actually selling equity, especially if you are intending on raising $50,000 - $100,000. Happy to schedule a call with you to provide more specifics and encourage you to read through the answers I've provided re fundraising advice to early-stage companies as well.Tom WilliamsTW
-
Any opinions on raising money on Indiegogo for an app?
Apps are difficult to fund on IndieGoGo as few are successful, and we rarely take them on as clients. Websites like http://appsfunder.com/ are made for that very reason, but again, difficult to build enough of a following willing to pay top dollar for an app that could very well be free, already existing in the marketplace. A site that is gaining more traction you may want to look into would be http://appsplit.com/. Again, Appsplit Is Crowdfunding For Apps specifically.Roy Morejon - Innovation Expert (Kickstarter, AI, Business Strategy)RM
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.
