Help for owners
My developer says what I asked for is impossible
Short answer
'Impossible' in software usually means one of three things: it is truly not allowed or not available, it is hard and costly with the current design, or the developer does not know how. Ask for the reason in writing, then get a short second opinion on that single feature before you drop the idea.
Does this sound like your situation?
- My developer says a feature cannot be done and gives no clear reason.
- The quote for a small change looks far out of proportion.
- Other apps do this feature, yet I am told it cannot be done in mine.
- I am told to rebuild everything for one change.
- I do not know whether to trust the answer.
Why does this happen?
It is blocked by a rule outside the code
Sometimes a store, a payment provider or a law really does forbid the idea. That is a true 'no' and a second developer would give the same answer.
It is possible, but the current design makes it expensive
If the app was built without room for a feature, adding it may mean reworking a large part. The developer says 'impossible' when the honest sentence is 'impossible without a big rework'.
The developer lacks that particular skill
Maps, payments, real-time chat, offline sync or video each need experience. A capable developer may not have it and will say it cannot be done instead of saying 'I have not done this'.
The request was understood differently
A feature described in business words can be heard as something much bigger than you meant. A simpler version may be possible even when the full idea is not.
What can I do about it today?
- Ask for the reason in one paragraphIs it forbidden, too expensive, or unknown? A developer who knows the answer can write it in a few sentences.
- Write the feature as what a user doesFor example, 'a customer taps reorder and sees the last basket'. A short description in user steps makes it easy for any engineer to judge.
- Ask what the smallest version would beA reduced version often delivers most of the value at a fraction of the effort.
- Ask for a short second opinion on that one feature onlyYou do not need to hand over the whole project or change developers. Send the feature description and the first developer's reason, and ask for a view of what is realistic.
- Do not stop the current work over one disagreementKeep the rest of the project moving while the one question is answered.
When should I bring someone in?
- The reason is vague, and the answer changes when you ask again.
- You are told to rebuild everything for a change that sounds small.
- A launch depends on the feature, and you cannot judge the answer.
How do I handle it?
- Read the request and the reason givenI take the feature as you described it and the objection as your developer stated it, without assuming either is wrong.
- Look at the code where the feature would liveI check how hard it really is inside the existing app and tell you if the problem is the idea or the way the app was built.
- Write a short opinion you can useIt says possible, possible with a rework, or not possible and why. It names the cheaper alternatives, if any, and the risks.
- Leave the decision with youYou can take the opinion back to your developer, ask me to build it, or drop the idea. I do not push for more work than needed.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Does a second opinion mean I am replacing my developer?
No. It is a review of one question. Many owners take the answer back to their current developer and keep working together.
Can anything truly be impossible?
Yes, when a store, a payment provider or a law does not allow it. I check that rule first and I will say so when the answer is no.
What do I need to send?
The feature written as user steps, your developer's reason, and access to read the code if the answer depends on it. No passwords are needed for a first opinion.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.