Loading...
Answers
MenuWhat is the minimum number of hours it would take to code an OpenTable app in appearance, features, and function?
Main function: calendar for reserving, list/map view of available restaurants nearby, search by filters, restaurant profile.
App would exclude the "points" / loyalty program features.
Answers
Knowledge source:- I'm an app developer myself (heading app development company www.agicent.com.
I believe you understand that an App like OpenTable basically has 3 major parts;
1. one is the end user App that you see on the front end on iOS or Android, (native)
2. Another is an App or a web portal for restaurant owners to receive and confirm bookings, see orders etc.
3. and a Backend that you don't see (which has the DB, APIs, business logic, Admin panel, reports etc).
So broadly breaking up these modules, I can do this project as follows:-
1. Minimum 60 to 80 hours for all UI design.
2. 350 hours for iPhone App for end user
3. 250 hours for An app (iPhone or android or web) for the restro owners.
4. Minimum 400 hours for the backend (DB design, API, admin panel with basic features).
5. An overall 150 hours of QA for each module.
6. Take a buffer of 10 % minimum.
These hours also include the research and planning on technology, third party libraries to use, and interim releases (at least 10 for both apps and admin etc) for your testing.
To get this done you need to have a great tech. architect cum supervisor who shall oversee and decide on everything, very good developers for iOS and Android (at least 1 senior + 1 assistant each), and a DB programmer and one Web developer (for admin panel), and a critical QA.
The actual release time of this whole thing could be:-
1. 3 months from scratch to one App (end user) and backend (without Admin panel).
2. Another 1 month for restro owners' app (or site)
3. Another 1 month for admin panel release and to finish everything.
While an offshore app development agency like mine would charge somewhere around $ 20-25 K for this project, the same in the USA would charge you 5-6 times, while the same in freelancers world could be done in like even less than 5 K (but that won't be what opentable is).
Feel free to ask more, I'm happy to assist.
PS:- some relevant apps from my portfolio
• Food ordering Apps - https://goo.gl/lb8Tfg , https://goo.gl/WTzXy2
• Limosine (Cab) Booking App (For a startup in Boston area, USA)- https://goo.gl/iIi2qs
And couple of more I'm getting done right now and wouldn't mind demo that.
The iPhone app it self could be done in 160 hours but I'm assuming that the backend and all the APIs are already developed.
I can help you build a detailed backlog / estimate if necessary.
I own a mobile app develop agency for the last 15 years. Few other requested apps like opentable before.
To create the main functionality of opentable - web app, mobile app, main management panel, restaurant app) from scratch it would take around 2500-3000 ours of coding. this is based on estimate one year back and assuming you are starting from scratch.
If you were to customize existing platforms like iScripts UberforX it would be closer to 500-750 hours.
Related Questions
-
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.DM
-
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
-
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
-
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
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.