ignition wrote:We're based in central London; do you know of any reputable full stack developers or agencies that would be worth meeting with to discuss our project? I'm struggling a bit with Google as the majority of results are job adverts!
I can put you in touch with highly regarded independent developers in Brighton don't use an agency as it will cost you 5x as much in money and endless meetings. Let me forward your brief next Tuesday and I'll see if anyone is available. You could hire me for the Website and overall design if you want. Just saying!
Some very brief answers to your questions as to be honest I don't want to end up consulting in a forum post.
1. It's feasible combining an open source CMS with modifications. Open Source does NOT mean "free". It depends whether you mean financial or technical feasibility. In the former case, prepare to spend and manage the goals of this project very carefully, in the latter case, anything is possible.
2. Yes and no. Publishing is a part of every CMS, central database extraction of specific texts and how you want to store/manage them is not. So you make that part.
3. It depends. Some developers focus on programming languages specific to Android and/or iOS. Others consider both platforms (mobile and desktop) "apps" in general. You probably want someone who can do both or partner with someone who can, so there's communication and some level of feature parity and consistency etc.
4. That depends pretty much entirely on you. Depending on how productive the project is anywhere between 12 and 24 weeks. Consider the cost triangle. It will be a mixture of open source components with the developer focusing on the bespoke parts. There is no off the shelf for this. It's too specific.
5. Depending on the pedigree of the developer and whether you can reduce the scope or phase the project between 2 and 7 grand including the mobile app. It won't be cheap. You need to consult to find this out.
6. Pay per page is nonsense. It's just a way to make pricing simpler. How much WYSIWYG varies massively. Implementation of things much like BBCode (normally called shortcodes) can help. The more control you want, generally the more investment you need to make. Layout is the least realistic. If you want that, you probably need to learn HTML or have a range of templates built in for you. You should be able to update the site, sure, but don't expect to rewrite the thing. After all, you could end up ruining it. You will need training and a content management role that all comes into costing.
7. Security updates and bug fixes depends on the complexity of the system. Most developers set up a bespoke maintenance contact for you. As hourly/day rates vary from around £100/d (Junior) to £500/d (veteran) - do the math. An hour or so per week would make sense. You might also need email support. You want a good relationship with your developer.
8. Too many questions, sorry. Referrals are probably best.
9. Speculative features and hypothesis Vs actually feasible features. With regards to layout, you should be using wire frames and possibly prototyping. Going through the design process in stages like information hierarchy, wire frames, mockups, designs, (prototypes), build, test, iterate avoids miscommunication. Don't just send a brief and hope for the best. Follow up on your prerequisites. If your developer needs something, give it to them.
10. Erm. I'll try to think of some. This stuff comes from a lot of experience.
Feel free to email me at
ben@bjum.uk if you need more.