Loading...
Answers
MenuWould my "Shazam" like idea work for a furniture purchasing app?
Answers
This idea is very intriguing. I believe the product is very doable if you have the appropriate tech resources and the right team. I'm unsure of what the target market may be for this application? Middle-aged individuals? And are you planning to make this free because I'm not too sure people will be willing to pay for this unless it has more attractive features. I would love to talk further about this and help you brainstorm some concepts + viable business models. Ping me!
The idea is great !! Its not new though..
Check out http://www.pounce.mobi/ ( it was earlier called BuyCode).
Some positive points
1) Just because it is there, it does not mean you can build it.
2) A business which got acquired and vc backed is a good sign that your idea is already market validated.
3) Because it is validated, you already know what is the market segment you need to target or you can pivot from the known reference point now.. cool ..isn't...
How can you do it ?
1) Ideas are dime a dozen and worth a shit. Don't feel bad. Build an MVP.
2) With the image recognition already democratized using dozens of cloud service providers, you should be able to build something quick with low TCO (total cost of ownership).
3) Identify your business model. You want to copy BuyCode or do something different ?
4) Try selling it - (rubber meets the road). You will feel the heat and smell the burns :-)
Need help ? talk to me.
I love this idea and would use it, don't listen to the naysayers. There have been previous attempts but that should only validate the need.
As a homeowner I would want this, and this would be useful to pretty much anyone looking for non-discount furniture (I say that because the IKEA demographic probably doesn't have time, money, or interest). I hated driving from furniture store to furniture store, and searching online would take many hours.
This would require a huge database of items. Maybe the vendors and manufacturers would give you photos to match against? make your vendors work for you if you can show that you could generate them business.
I think you are going to need some of the following consultants: furniture historian to help categorize older furniture, furniture designer to help sort into categories, a software developer to figure out how to match the image to a database, someone to work with manufacturers, and a lot of people to enter information.
Cool idea. Biggest question is market size. I presume the furniture market is big -- the question will be how many people will shazam furniture and what kind of revenue could you generate from those purchases? Maybe the broader opportunity is to shazam any product you can buy...
Related Questions
-
If I am planning to launch a mobile app, do I need to register as a company before the launch?
I developed and published mobile apps as an individual for several years, and only formed a corporation later as things grew and it made sense. As far as Apple's App Store and Google Play are concerned, you can register as an individual developer without having a corporation. I'd be happy to help further over a call if you have any additional questions. Best of luck with your mobile app!AM
-
Where can I find programmers willing to join a growing mobile start up for equity only?
You won't find anyone worth adding to your team willing to work for equity only, no matter how compelling your product and business is. The realities of the talent market for mobile developers anywhere is such that a developer would be foolish to work only for equity unless they are a cofounder and have double digit equity. Happy to talk about hiring and alternatives to full-time hires.TW
-
What is the best technology for developing a new mobile app from scratch?
There are two sides to that question. One is the mobile app itself and the other is the backend. If I misunderstood in any way and you didn't mean "native" app I apologize in advance. On the backend, there is no clear cut answer to which is the "best". It depends solely on the developers you are able to get. We for example use Node.js , mongoDB, redis, elasticsearch and a couple of proprietary tools in the backend. But you have your pick of the litter now both on the backend api and the datastore with the myriad of options available and touted as the "best" currently on the market. Now on the app side again it solely depends on what you need your mobile app to do. Experiencing first-hand "develop once, run anywhere" I can say it's more like "develop once, debug everywhere" to quote a Java saying. We have tried Phonegap and Titanium Appcelerator and we have switched to native (ObjC and Java) after a couple of months of trying to go the hybrid route. The reasons behind the choice are as follows: - anything that breaks the pattern of how those frameworks NEED to operate is just a huge technical debt that keeps accruing a huge interest. - anything that uses css3 accelerated animations on Android is buggy at best and slow as hell at worst on any lower (< 4.1 I think) versions of Android I hope this gives you some insight. If you need/want to ask me anything feel free to contact me. MihaiMP
-
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.DM
-
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.TW
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.