Quote:
Originally Posted by maxtower
Do you already have a design in mind?
Yes I've put together the specs already so I'm mainly concerned with the developer creating what I've put together
Quote:
Originally Posted by maxtower
If you post all of your specs here, someone can help with the hours estimate.
I'm having trouble getting the image posted on here, but in a nutshell I'd like the main screen to be similar to the main screen of the bravo app, but:
- instead of showing casinos, I'd like it to show basketball courts
(I'd prefer the most efficient, cost effective way but what I'm thinking is the app takes the users location, queries a database, and returns the results sorted by proximity)
- instead of showing the # of tables, I'd like it to show the # of people at that location with the app open
- Also, the bottom inch of the screen would display banner ads
There would be 3 buttons:
- the refresh button that refreshes the users location and subsequent data
- a button that takes the user to a screen with just text (this is the 'About' screen)
- a button that takes the user to a text box where they can enter feedback (a 'send' button on that screen would send their message to an email address)
- Also, on the 'About' and 'Feedback' screens there would be a 'Home' button to bring the user back to the main screen.
Quote:
Originally Posted by maxtower
Are you ever planning to also launch on Android? If so, there may be multiplatform issues to consider.
That's a good question. Ideally yes but I'm not sure how that affects things, what should I be considering? I have limited knowledge, but I thought Phonegap could be used for this.
The short answer is I'd prefer the app to be developed for both platforms but only if:
- costs were similar to iOS only
- the app could be accepted in both stores
Quote:
Originally Posted by maxtower
You probably don't need much project tracking for such a small project. Maybe a spreadsheet would be good. Take each screen as a milestone maybe?
This seems like a good idea, I guess the backend would be a milestone too?
Quote:
Originally Posted by maxtower
On the backend, be careful of anyone who tries to sell you their "solution". It is likely they could give you a generic backend either BaaS or a pile of code that you can take and install on another server if you want to. Bottomline is you don't want to be at your developer's mercy on the backend for the life of the product.
This does worry me. I feel like architecture-wise I'd like the backend developed so that it can be scaled fairly easily. I don't know much about this area except it may require a rest api or parse?
Thanks for the detailed response.