I need a qualified and experienced developer to build a mobile app for an existing OpenCart website. Please prepare your proposals with any similar work you have previously done or with reference to any ready made software solution. I can purchase any plugin/ready made code/app source code (there are some products when you make a google search) you suggest that will boost the speed of the project. Please write me back with any consideration or suggestion you have.
Brandon S.100% (1)
Create an account now and send a proposal now to get this job.Sign up
Clarification Board Ask a Question
Can we use existing opencart apps for that? Couple of more questions, so have any chance to discuss with you in details ?
I look forward to your response.
a couple of quick question if I may to make sure I am sending the right information on my proposal:
- Which version of Opencart are you running?
- Would you prefer for the website to be wrapped up as a simple browser page inside an app (a little bit of lag/latency on first page load)
- ...or would you prefer for this to be a fully natively coded app (preference for user experience)
- Aside from the standard Opencart setup on the site itself, are there any major modifications to the site?
I think that's pretty much everything I need to know.
SteveBrandon S.24 May 2018
It's OpenCart version 2.3. I'm not expecting it to be native code as long as it's working smoothly. For the mobile app I don't need any custom module functionality although the payment gateway is Stripe (I need Stripe payment module which is not a default functionality of OpenCart as per my understanding).Steven T.24 May 2018
thanks for getting back to me. From what you've said there may be a slight conflict on the requirements.
If we go non-native (hybrid) then we'll be wrapping up the website inside a WKWebView. This basically creates a Safari-style window to your website inside the app. This means that the app would use the existing payment routes and everything else set up on the existing website. If you need to integrate Stripe, then this should be done at the website end, rather than inside the app.
It may be possible to create a call back to the app from the payment button, but then it can get messy sending the purchases back to your site for stock-control, etc.
If we need to integrate Stripe then we'd be better off by far to code it natively using API calls to your site's database for the information it needs, and then integrate Stripe at the payment end of the transaction.
It requires more work as the screens will need to be set up individually, but this can be expedited by using a suitable e-commerce template from the likes of CodeCanyon. The template would then be manipulated to marry up with your site's look-and-feel.
What are your thoughts on this? Either way will work. Going Hybrid will mean it's a lower cost to develop, but the flow will be controlled entirely by your website. Going Native you'll get proper iOS look and feel, Bespoke operations to suit your needs, but would take a little longer to develop, increased costs.
The big question is: What is your preference?