After doing more research, I don't want to rely on API's for my app. I am not a very graphically creative person so sketching a prototype has been really difficult for me so far, though I am forcing myself to make it. When it comes to the MVP, I haven't had the chance to pick up the book yet, so I cant say much about it. Though to make this app what it ultimately should be, there isn't much I can cut off from the current plan, IMO anyway. Would you (or anyone here for that matter) be able to give me a rough idea of how much I should expect this to cost? The backbone of the of the app is very complex, and Id like the U.I. to be as simple to use as possible. I want to at least launch it on the android and Ios devices, with a website, and a cloud based software. Though Im trying to think of a better way to make it cheaper/easier for others to integrate on the business level.Dylan seems to be on the dev side. I am on the business side, so here is what I worry about when building an app:
When you depend on an API integration for your app to function, remember that support and escalation paths need to be nailed down early. Where-ever possible, I will house data internally and draw upon it, vs. depending on a third party who has other customers and revenue models to keep an eye on as well.
Prototypes are always best started with pen and paper. Draw, scratch, re-draw, test. One page per step in the workflow and then test it on someone--anyone. Then translate what comes of it to the PC and link them together in a low-fidelity mock-up.
As far as simplicity--read Eric Ries' Lean Startup and introduce yourself to the idea of an MVP, or Minimum Viable Product. The idea is to build only the necessities, test, fail quickly if needed, and decide next steps.
Make no mistake, this is a complicated process, but it's a very fun and lucrative complicated process.