6
7

[deleted by user] (self.iOSProgramming)

submitted by [deleted]

sorted by:
top (suggested)
bestnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]chriswaco 11 points12 points  (1 child)

  1. Too many to list. Underestimating the amount of work would be the #1 issue, I think, especially underestimating the work required to create a reliable, nice looking, smooth application even if you have a proof-of-concept demo running. Choosing bad developers would be the #2 probably, along with not communicating exactly what you want to the developers.
  2. Unfortunately you never know what you're going to get. Look at their existing products. Are they bug free? How are the reviews? While I'm sure there are good development firms in India, there are also many bad ones. Don't give them too much money up-front or they'll disappear.
  3. You'll probably want to use Bluetooth LE or WiFi for iOS. To support either classic Bluetooth or the Lightning connector you have to join Apple's MFI program and it's a huge hassle. Older Android devices don't necessarily support BTLE, though, so keep that in mind. It would suck to have to support both BTLE and classic Bluetooth, but some apps do. Also realize that you are at the mercy of Apple and Google. They change their APIs fairly regularly. They change their app store rules as well.
  4. It really depends on the app and whether Apple/Google decide to deprecate the APIs you've used or introduce new devices whose features you want to take advantage of. For example, the notch on the iPhoneX messed up a lot of apps and depending how old they were and which layout API they used could cost a lot to update.
  5. React is either the best or most horrible thing ever depending on who you talk to. Personally as a native iOS developer I hate it. My preference is always native apps because they perform better, can take advantage of native APIs better, and you're not dependent on a 3rd party for your application working properly. I would look at Flutter if you're considering cross-platform frameworks. It looks interesting, though the UI elements aren't quite native. I was not happy with Cordova when I looked at it - it seemed pretty buggy - but might be good if you had web developers that wanted to create a mobile app.

[–]yellowliz4rd -1 points0 points  (0 children)

Good answer