Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • I understand, and mostly agree, but in this case I am locked into the Apple ecosystem, for some reasons, especially because the client already bought the iPad... Commented Jul 26, 2012 at 22:51
  • 1
    I would pass the responsibility for licenses to the customer. I assume the end software will be owned by them. In that case, they should pay any ongoing license fees, not you. You could look at a 1 off fee of $99.00 (Put as a line item on your invoice "Apple Taxes"), and make it clear that the end of each year they must pay another $99.00 if required by the license. (Not too many years before that iPad starts looking pretty expensive against a Samsung.) BTW- a 1 off $100 is chicken feed when talking about software development. If it's of concern, the entire project is a concern. Commented Jul 27, 2012 at 2:32
  • That's very good advice, thanks. However, regardless of who will be paying for the licenses, it bothers me a lot that the app still must be updated every year, or it will stop working. It's extra work that I'm not willing to do - even if I charge them for it. Commented Jul 27, 2012 at 15:20
  • 1
    Basic requirements management dictates that the requirement drives technology. In this case "Must use IPad" - technology has become a requirement, that is conflicting with other requirements. The resolution of this conflict needs to be addressed before the project starts. Commented Jul 31, 2012 at 21:49
  • You are right in every aspect. Although this won't solve my immediate problem (and that's why I accepted a different answer), I'll definitely keep it in mind for future projects. Commented Aug 6, 2012 at 22:05