14
gitpush
5y

TL;DR;

I was asked to give estimation on an app, that:
1. No one has a clue what it does, even though there is v1 on the store with almost 10% of functionality working
2. No one has a clue what should be in the new rewritten version
3. We are already behind schedule and I have no clue why, I've just been told that
4. They need UI flow that shows how the app will work with static data and when API's are ready (because ya know, writing code is easier than creating wireframes and modifying them accordingly) I will then need to link app with API as if it is as simple as drinking a cup of water, especially that: 1. What is water? 2. Do I have a cup or is it given, and 3. Relax bro, drinking water is like eating a burger, piece of cake!

I'm not sure what to do, not enough that it's React Native but also spaghetti requirements that no one was able to answer my simple question: What is the app responsible of?

P.S.: Some say I must rewrite the old app ONLY, no new features, others say: Turn the new web portal into mobile app, I say: WTF is going one?

Comments
  • 7
    Run, run away while you still can!!

    This is just another day in my life so I completely respect the "wtf do you even want" thought you had!
  • 2
    @C0D4 I'll try to get things back on track by at least managing tasks they want, wish me luck, I honestly have no clue how to react in this situation lol

    @Frederick T_T
  • 4
    Ask for written requirements, then base your estimate on that. Agree with your client on that estimate in combination with your estimate (written!).

    If they don't have written requirements, say 2 years, maybe more, maybe less. Spagetti requirements result in spagetti estimates...
  • 1
    @kolaente Thanks man, I'll push for that. not to be pessimistic, assuming I got nothing, how do you react in this case?
  • 4
  • 3
    @gitpush You could also sit down with the client, ask him precisely what he wants, then agree on that. Or agree with him (again, written) on some kind of contract where you are paid by the hour. Then ask for something to start with, and charge for every little bit he wants after that.

    You could also propose him both ways, saying the first one will be more efficient (and as such, less expensive) and let him decide what he wants.

    You should have some kind of contract though before starting any work on the actual app.
Add Comment