Pre Release nerves/anxiety

[MikeH]

Does anyone else get this?

You already spent forever developing your app. You test, tweak, debug, debug some more, test again, debug, test again... maybe debug more... over and over until finally you think you're ready to release your fully working, shiny new app to the store. But wait! What if:

...it crashes on startup? - but it doesn't for you
...it crashes anywhere at all? - but it doesn't for you
...those new features don't work as expected? - but they do for you
...ads don't work and you stop earning? - but they do for you
...Google/Apple reject your app? - errr that's in the hands of the Google/Apple gods but you *think* you followed all of their rules and the previous version was fine
...users don't like it any more, say you've ruined a perfectly good app, leave bad feedback, then uninstall? - but you made improvements, right?

So, if you're like me, you get stuck in the eternal loop of "test, debug, repeat"... and during that time you think of a new feature (or 10) - so that makes the test/debug loop even longer and you think to yourself: "When will this app ever get released???"

Your thoughts?

 

[Sandman]

Nope, that's just you.

Just kidding, I imagine you're describing many of us here. And there are some scenarios where you just can't win. A couple of years ago I had a new version of my app, which started at boot, that I pushed to the store. Tested on several android versions so I felt good about the launch. Turns out one customer had an unusual Sony model that I didn't have and therefore had not tested on. When the customer ran the app it crashed the OS, with lots and lots of horrible visual glitching on the display. So he force-rebooted it. And - remember? - my phone started at boot. So another crash. Force-reboot. Hilarity ensued. (Not.)

But seriously, you need to get a grip on that feature creep. I'm in the other direction, the closer to deadline I get the more planned features I axe from the todo-list.

 

[AnandGupta]

I have uploaded one app in Google Play Store recently.

Before that I tried to upload one app, 2 years ago, but was rejected by Google for failing some requirements.
But I learnt. Just make the basic feature of the app and upload.
If it has minimum features and code then less chance of getting rejected.

Next keep adding more features and update the same. Do not rush with all features in one go. You may make mistake in some code somewhere and Google will reject it.
I follow this routine and it is all Okay.

 

[LucaMs]

Your thoughts?

I was in the wrong profession, I should have been a politician.

 

[BlueVision]

Well...
I don't publish app's in the playstore, but:
My previous projects have received mostly positive feedback. Why?

You can't be prepared for all eventualities.
"IDIOTS ARE INVENTIVE..."
The app? As simple as it can be with basic functions that work, no one expects a premium version of a good idea right away. Then the moment has come for the release.
I think it's better to react quickly to feedback in order to recognise the needs of customers, set priorities accordingly and improve the app step by step. Evolution is the key. That creates the feeling in the customer that you are taken seriously, that you are reacting to problems and improving the app. This also creates a little patience and trust.
I've managed quite well with this tactic so far. There has almost always been friendly and constructive feedback. Even if sometimes not everything goes perfectly right away.

 

[aminoacid]

I have uploaded one app in Google Play Store recently.

Before that I tried to upload one app, 2 years ago, but was rejected by Google for failing some requirements.
But I learnt. Just make the basic feature of the app and upload.
If it has minimum features and code then less chance of getting rejected.

Next keep adding more features and update the same. Do not rush with all features in one go. You may make mistake in some code somewhere and Google will reject it.
I follow this routine and it is all Okay.

Right on ... That's exactly what I have done in the past and have never been rejected. They tend to scrutinize the initial release much much more than the updates.

 

[Hamied Abou Hulaikah]

switch to games development, no headache after published, no clients need support, no fix is urgent and the best is a lot of simple people will play it
Games development is publish and earn.

 

[MikeH]

I was in the wrong profession, I should have been a politician.

I disagree, comedian is more your calling

 

[MikeH]

Nope, that's just you.

Just kidding, I imagine you're describing many of us here. And there are some scenarios where you just can't win. A couple of years ago I had a new version of my app, which started at boot, that I pushed to the store. Tested on several android versions so I felt good about the launch. Turns out one customer had an unusual Sony model that I didn't have and therefore had not tested on. When the customer ran the app it crashed the OS, with lots and lots of horrible visual glitching on the display. So he force-rebooted it. And - remember? - my phone started at boot. So another crash. Force-reboot. Hilarity ensued. (Not.)

But seriously, you need to get a grip on that feature creep. I'm in the other direction, the closer to deadline I get the more planned features I axe from the todo-list.

Feature creep - yeah - but I love coding, I'm addicted

 

[MikeH]

Well...
I don't publish app's in the playstore, but:
My previous projects have received mostly positive feedback. Why?

You can't be prepared for all eventualities.
"IDIOTS ARE INVENTIVE..."
The app? As simple as it can be with basic functions that work, no one expects a premium version of a good idea right away. Then the moment has come for the release.
I think it's better to react quickly to feedback in order to recognise the needs of customers, set priorities accordingly and improve the app step by step. Evolution is the key. That creates the feeling in the customer that you are taken seriously, that you are reacting to problems and improving the app. This also creates a little patience and trust.
I've managed quite well with this tactic so far. There has almost always been friendly and constructive feedback. Even if sometimes not everything goes perfectly right away.

I have uploaded one app in Google Play Store recently.

Before that I tried to upload one app, 2 years ago, but was rejected by Google for failing some requirements.
But I learnt. Just make the basic feature of the app and upload.
If it has minimum features and code then less chance of getting rejected.

Next keep adding more features and update the same. Do not rush with all features in one go. You may make mistake in some code somewhere and Google will reject it.
I follow this routine and it is all Okay.

My main two apps are about 7-8 years old and get an update about 2 or 3 times a year. Maybe my anxiety is more to do with other things happening in my life now.

 

[MikeH]

switch to games development, no headache after published, no clients need support, no fix is urgent and the best is a lot of simple people will play it
Games development is publish and earn.

I have a few simple games out already but they dont interest me as much as utility apps - also my games get very few downloads ?‍

 

[MikeH]

So rather than publishing the updated app that prompted this thread, I spent a few days updating another app. Now they're both ready for release. I'm going to aim for that day to be today... just have to cross my fingers and hope. Thanks everyone, I've enjoyed your replies ?

 

[Andris]

Mike, I totally get it. You've described the development cycle perfectly. I have an app that seems to have been 99% done for a few years now ... at any point in time, I've felt like 99% of the remaining work has been done, only to realize something else just has to be done to prevent that initial negative user experience. And it has to be done for both Android and Apple, because it's not a serious app unless it's offered for both.

My family is so used to me sitting there "putting the final touches" on my app that they don't even ask about it any more. When friends ask me what I'm doing with my time, I'm at the point where it almost pains me to say the words "my app" because it's what I told them last year. LOL!

I'm fortunate that I don't have to depend on app development for survival. If I were, I'm sure things would have gone way faster. But the bottom line is I love doing this. I love using Erel's fantastic tools and being part of this awesome development community. Perfecting an app gives you a feeling of empowerment, and it's a power that grows as you get more skilled with B4X.

I like comparing the development process to writing a novel (which I've never done). The number of words is similar, and the structure and resolution of plot and ideas and character interrelationships are just as complex, while keeping it easily readable. If someone writes a novel in a couple of years, that's considered fast. Thinking this way makes me feel way better about my development speed!

Just embrace the process. It's more satisfying than the result anyway (haha). BTW my app is just about done ... very shortly ... I'll post the link here on the forum when it happens ... ?

 

[KMatle]

Experience is important and to really learn from your errors. At work I always except the worst (doing backups of data or files before I handle them). Saved me (or the company) once or twice

 

[AnandGupta]

Experience is important and to really learn from your errors. At work I always except the worst (doing backups of data or files before I handle them). Saved me (or the company) once or twice

Yes, I too have lost code once, due to overwritten by mistake. Now I always backup codes daily, before I start work. Also helps to find the changes I made.