3 ms·

Currently I am also spending time learn iOS to build an app. And its a long arduous task, specially if someone has never coded ever. Personally, last I wrote a

Currently I am also spending time learn iOS to build an app. And its a long arduous task, specially if someone has never coded ever. Personally, last I wrote a piece of code was 3+ years ago, while in school. I haven't specifically shopped for a developer cause forget $50k, I can't even spend $5k. So I guess sometimes, its not really about offsetting your potential earnings, than it is about whether you could afford one at all. Still it will be interesting if ThomPete ever publishes his earning report of sorts :) PS: Just wondering any specific course/book you are referring for iOS?

ThomPete 12y ago
I think if you have an interesting problem it's easier to get a developer on board than if you have something thats a lot of work but tedious to do. Also I always offer 50/50 split after I have recouped my investment. This is to pay for upgrading the app (an there will be many updates after launch believe me). If the app is interesting then they might be a little more willing to invest their time too.
- thisisit 12y ago
  A query, how did you decide on the price point for your app? There must be some kind of break-even calculation or something?
  - ThomPete 12y ago
    I learned the hard way it's better to start low and the raise prices than to start high and then have to lower them. You wanna give the early adopters a better deal than the later ones. I knew this app was unique (I frankly have never seen anything close to it) and i knew it was adding value because I use it all the time myself and it has some potential so I could go way higher and still make the same if not more. But I decided to start at this price because i didn't know what kind of bugs would surface once many people started using it. That way people don't feel like they are overpaying even when they find bugs and I am kind of giving them a discount to provide me with valuable information. I think that is fair to everyone.
ryanSrich 12y ago
I'm working through this course - http://bitfountain.io/courses/complete-ios8 http://bitfountain.io/courses/complete-ios8 It's really comprehensive but absolutely massive. If you have a demanding full time job it could easily take you a year to get through the full course. > I haven't specifically shopped for a developer cause forget $50k, I can't even spend $5k. The problem isn't really the initial dollar amount, it's spending what you think you can make back on the application in a reasonable amount of time (6 months). If you can't make $50k on an app then why spend the money to have it made? On the other hand if you can spend 3-4 hours per week learning how to build the app then what you make back is really whatever you value your time at minus the upside of learning a new skill. The problem is that it takes years of experience using these tools and programming in order to make anything complex. I'm learning that the hard way.
- thisisit 12y ago
  > The problem isn't really the initial dollar amount, it's spending what you think you can make back on the application in a reasonable amount of time (6 months). If you can't make $50k on an app then why spend the money to have it made? I guess that is where one needs to a fair bit of market analysis. One could argue that ghostnote might or might have a potential for $50k but who knows? Add the fact that some gurus say paid apps are dead while you can find numerous paid ones working fine, it is just confusing. Then there is decision on pricing the app. I was reading up on some devs who put out their income figures. One might be inclined to think Dash for iOS at $10 might be a hard sell but it has done really good. On comparing to another app priced at $3.99 with same number of downloads, the returns have been much higher. So the issue doesn't stop with whether I can make it back. But also, how do I make it back. I am too learning it the hard way :) > I'm working through this course - http://bitfountain.io/courses/complete-ios8 http://bitfountain.io/courses/complete-ios8 My first impression after scrolling through the page is - It is too detailed. Maybe for complete beginners in programming. I have started with free Udemy course - https://www.udacity.com/course/ud585 https://www.udacity.com/course/ud585 Following it up with the free Stanford classes. Currently need to start with the 3rd lecture.

ThomPete 12y ago

I think if you have an interesting problem it's easier to get a developer on board than if you have something thats a lot of work but tedious to do. Also I always offer 50/50 split after I have recouped my investment. This is to pay for upgrading the app (an there will be many updates after launch believe me). If the app is interesting then they might be a little more willing to invest their time too.

thisisit 12y ago
A query, how did you decide on the price point for your app? There must be some kind of break-even calculation or something?
- ThomPete 12y ago
  I learned the hard way it's better to start low and the raise prices than to start high and then have to lower them. You wanna give the early adopters a better deal than the later ones. I knew this app was unique (I frankly have never seen anything close to it) and i knew it was adding value because I use it all the time myself and it has some potential so I could go way higher and still make the same if not more. But I decided to start at this price because i didn't know what kind of bugs would surface once many people started using it. That way people don't feel like they are overpaying even when they find bugs and I am kind of giving them a discount to provide me with valuable information. I think that is fair to everyone.

ryanSrich 12y ago

I'm working through this course - http://bitfountain.io/courses/complete-ios8 http://bitfountain.io/courses/complete-ios8 It's really comprehensive but absolutely massive. If you have a demanding full time job it could easily take you a year to get through the full course. > I haven't specifically shopped for a developer cause forget $50k, I can't even spend $5k. The problem isn't really the initial dollar amount, it's spending what you think you can make back on the application in a reasonable amount of time (6 months). If you can't make $50k on an app then why spend the money to have it made? On the other hand if you can spend 3-4 hours per week learning how to build the app then what you make back is really whatever you value your time at minus the upside of learning a new skill. The problem is that it takes years of experience using these tools and programming in order to make anything complex. I'm learning that the hard way.

thisisit 12y ago
> The problem isn't really the initial dollar amount, it's spending what you think you can make back on the application in a reasonable amount of time (6 months). If you can't make $50k on an app then why spend the money to have it made? I guess that is where one needs to a fair bit of market analysis. One could argue that ghostnote might or might have a potential for $50k but who knows? Add the fact that some gurus say paid apps are dead while you can find numerous paid ones working fine, it is just confusing. Then there is decision on pricing the app. I was reading up on some devs who put out their income figures. One might be inclined to think Dash for iOS at $10 might be a hard sell but it has done really good. On comparing to another app priced at $3.99 with same number of downloads, the returns have been much higher. So the issue doesn't stop with whether I can make it back. But also, how do I make it back. I am too learning it the hard way :) > I'm working through this course - http://bitfountain.io/courses/complete-ios8 http://bitfountain.io/courses/complete-ios8 My first impression after scrolling through the page is - It is too detailed. Maybe for complete beginners in programming. I have started with free Udemy course - https://www.udacity.com/course/ud585 https://www.udacity.com/course/ud585 Following it up with the free Stanford classes. Currently need to start with the 3rd lecture.