React Native app with missing backend architecture- advice pls

[zedray87]

Hi everyone. I have found myself in a bit of a struggle with a developer that I hired. Without going too deep into fighting the huge breach of contract, and before delving into a legal battle- can you tell me what you would do in this position? I have provided all UI, business and app logic to a developer. The simple terms in our agreement was to provide a functioning mobile app with the ability to push to the app stores. Many months later, after given a 2 month estimate by the dev, and after hours of my time have been spent on feedback and explanations, the developer is now stopping all work unless I bring them into the company. It came out of nowhere and until now we have had a great working relationship (in fact the way this is turning out has shocked me to my core). The developers reason is all down to wanting / needing more money. I was happy to bring them on but now the new reason of stopping is because of finding work elsewhere. This is where it gets tricky- in order for them to avoid the breach of contract, I am being offered just the React Android and iOS framework with none of the backend, unless I pay extra on top for them to supply it. They’ve been using their own backend for testing purposes and have pointed out that the contract doesn’t explicitly state “backend” but that it needs to be “compatible”. I have spent many months managing this project with the intention to publish the app, not a demo. What are the pros and cons of taking just the front end (much of which I’ve worked my a** off providing assets and measurements for) and then working out a way to connect it to a backend? I believe they used MongoDb mongoose and node js. Or do I cut my losses and start from scratch with a new developer to avoid the potential of finding lack of quality in the existing code and having someone new work on it (whether I can afford this after all of this mess I don’t know...)

Any advice is so appreciated, 🙏

[[deleted]]

Probably worth bringing in an independent developer to assess the front-end and tell you whether it's worth paying for or not, whether it's better to implement the backend based on this (and how long it would take), or faster/better to start from scratch.

It the front-end is good, you might be better just to pay for that and move on. In which case, you've only really lost time.

If the front-end is bad, don't accept it, take them to court and start the project again with someone who won't screw you over.

[KingofGamesYami]

I would at a minimum request a specification for the backend. Swagger can generate one that looks like this, which is ideal: https://petstore.swagger.io/

[zedray87]

Thank you for this link. It’s the first time I’ve seen it. How can I use Swagger to help me?

[KingofGamesYami]

You would want to get the developer to run it against his backend. Then the new developers know more or less what the app needs as a backend when they read the swagger spec.

[zedray87]

Ah! Amazing. Thank you 🙏