|
|
|
|
|
|
by EvanMiller
4179 days ago
|
|
|
I received an interesting reply over email which I wanted to share here. With the author's permission I've reproduced it below but blanked out some details: > I (or we as a company) faced pretty similar situation just a few weeks ago. > The app is called ______, and it was our first app ever, our child - app that constituted our company brand and still is pretty useful for many small business owners (_______ is an invoicing app, making something like $20k/year on our domestic market). > Unfortunately(?) business is business, so finally I decided to decline it. Now we’re making some final touches and will release it as open source project - again facing similar problems - the codebase is almost 6y old, app is not trivial, build procedure is not single click etc etc. > Besides all those risks and problems, I still believe that opening the source code is worth doing. That way we can help other (less advanced) programmers to start their own mac products/businesses. I’m sure that you’ll agree that after a certain point you need to look inside something bigger than a trivial app from examples folder, something that is/was a real thing, something ‘alive'. That’s IMHO a single priceless source of practical knowledge. > That’s my 10cents :) |
|
|