So,i got this iOS social app built and

[lakerslive]

after 10 months of development, i started testing it. then the app kept crashing.

Programmer said, they have to optimize their code for another 1 -2 weeks.

BS?

1. is This a bad sign already that they overlooked lines of codes for this to happen in the first place?

2. Do they really sit 8 hours a day infront of pc "optimizing"

tnx

[sarettah]

Originally Posted by lakerslive

after 10 months of development, i started testing it. then the app kept crashing.

Programmer said, they have to optimize their code for another 1 -2 weeks.

BS?

1. is This a bad sign already that they overlooked lines of codes for this to happen in the first place?

2. Do they really sit 8 hours a day infront of pc "optimizing"

tnx

How long was development supposed to take? I assume they did up an estimate and produced a development plan of some kind before they started.

10 months does not really tell us anything. If it is an extremely complex app then 10 months might be a very short time. If it is a simple app then 10 months might be way long for it to take.

As far as programmers sitting 8 hours doing code, most of the time they do not. There are always meetings and phone calls that are occurring. Then of course there is client handling, putting out fires on the various projects they are supporting. When I do a project plan, even if I only have that one project going on, I never plan more than 20 hours of actual coding in any week. So a project that I quote with 1000 hours of coding with only one coder on it full time would be quoted as about 1 years worth of time.

It is not necesarilly a bad sign or a good sign. Shit always gets missed, even with the best people working on it. Did they invite you to start testing it? Or was that a demand you put on them?

I have clients that feel they need to see stuff in action very early, that means that what they see is often incomplete without any bugs worked out yet. That is explained to them beforehand and I use a different development methodology that I call "rapid fire programming" aka "Flying by the seat of my pants", but I do try to manage the client's expectations so that they are not disappointed.

So, like I say, you really don't give enough information for your questions to be answered, imho. No 2 jobs are the same so what applies to one may not apply to another.

.

[dillfly2000]

Originally Posted by lakerslive

after 10 months of development, i started testing it. then the app kept crashing.

Programmer said, they have to optimize their code for another 1 -2 weeks.

BS?

1. is This a bad sign already that they overlooked lines of codes for this to happen in the first place?

2. Do they really sit 8 hours a day infront of pc "optimizing"

tnx

Depends who you hired.

[VladS]

Can you give a little bit more details? Feel free to contact me directly if you can't say it here. Did you do any testing before or is this the first time you put the product to test? Do they use any development plan / guidelines or simply put you on hold for 10 months in blank?

That's why i like the Agile methodology when it comes to long term projects.