Do you build custom mobile apps, or just websites?
▼
Both — techs on FixlyDesk range from website builders (WordPress, Shopify, custom code) to app developers building for iOS, Android, and the web.
My website is down or was hacked — can someone fix it fast?
▼
Yes, submit a request marked urgent and describe what's happening — a tech can assess the issue and get you back online.
I don't have technical knowledge — can I still get a website or app built?
▼
Yes. Describe what you're looking for in plain language when you submit your request; a tech will scope the work with you before anything starts.
Is it worth fixing my old website, or should I just start over?
▼
That's a fair question to put to a tech before you commit to anything. If the site sits on a platform nobody maintains any more, runs plugins that have been abandoned, or was built by someone who's long gone, patching it can turn into more work than a clean rebuild — and a tech will usually tell you so rather than keep chipping away at it. If the structure is sound and it's just dated or has one thing broken, a repair or a refresh is normally the cheaper path.
If someone builds my website, do I own it — or am I stuck with them?
▼
You should own it, and it's much easier to settle that while the work is being scoped than afterwards. Ask that the domain is registered in your name, that the hosting account belongs to you, and that you get the logins and the site files once the work is done. That way you can hand things to a different tech later without starting from scratch.
Do I have to keep paying someone once the website is finished?
▼
Not necessarily, but a website isn't quite a one-and-done thing — platforms push updates, plugins go stale, and your domain and hosting renew on their own schedule with the providers you bought them from. Some people handle that upkeep themselves once a tech has walked them through where everything lives; others arrange periodic check-ins. It's worth asking whether ongoing maintenance is part of the quote or a separate arrangement, so it's clear from the start.
What should I have ready before I submit a request?
▼
For a repair, describe what you're seeing — the error message, the address of the site, and roughly when it started going wrong. For a build, it helps to have your text, photos and logo somewhere you can send them, a couple of examples of sites you like the look of, and a plain-language list of what the site needs to do. If you can dig out your domain and hosting logins, do; if you can't find them, just say so in the request, because tracking down access is a normal part of the job.