Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I need someone to add a feature to my app that already exists

Short answer

Adding a feature to a live app starts with reading the existing code, because a new piece has to fit what is already there. Prepare a clear description of the feature, access to the code and the store accounts, and agree a small first release before anything touches your live users.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I have a feature in mind and my current developer is not available.
  • Quotes differ widely because nobody has seen the code.
  • I am worried a change will break what already works.
  • I do not have the code or the store login.
  • The app was built by someone else and has no documentation.

Why does this happen?

  1. New work depends on old work

    A feature touches screens, data and sometimes the server. Without reading the code first, the effort and the risk are guesses.

  2. Access is often missing

    The code repository, the server and the store accounts may belong to a former developer.

  3. Platform rules change

    Stores set minimum technical requirements for updates, so an old app may need other changes before a new version can be released.

What can I do about it today?

  1. Describe the feature in plain wordsWho uses it, what they do, what they see, and what happens when something goes wrong. A sketch on paper is enough.
  2. Find your accessWho has the code, the server and the store accounts? Write the names down.
  3. Check the app still worksOpen the live app and note anything already broken, so it is not blamed on the new work.
  4. Decide what is essentialSeparate the part customers need first from extras that can follow.
  5. Do not ask for the change on the live appChanges should be tested on a copy first. A developer who offers to edit production directly is a risk.

When should I bring someone in?

  • You have no access to the code or the store accounts.
  • The app is old and may not meet current store rules.
  • The feature involves payments or personal data.

How do I handle it?

  1. Read before quotingI read the relevant code and run the app so the estimate is based on what exists.
  2. Write a short scopeThe feature, what it will not do, and how it will be tested.
  3. Build on a copyThe feature is built and tested away from your live app, with a backup before release.
  4. Release carefullyA tested rollback is ready when the update goes out.
  5. Leave notes behindWhat changed and why is written down so the next person can continue.

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?

Can you work on an app another developer built?

Yes, once I can read the code and run the app. If the code is not available, I tell you what can still be done.

Will the update break my app?

Every change carries risk, which is why I use a copy, a backup and a tested rollback.

Can you add a feature to a no-code app?

It depends on what the tool allows. I check this first and tell you.

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.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.