I am posting this question as I would need some good advice to start building my very first app.
First, I'd like to share the aim of the app: being able to take pictures from (different) mobile devices' cameras, having a graphic (like a mask, an image) showing up when looking into the camera. The intent is to have a virtual car which I can place next to real people when shooting my pictures, see the preview and save them.
My first thought was, not to cover how to build apps for different specific devices (e.g. android, iOS, windowsphone), to make a web app. I am fairly fine with programming and web frameworks in general. Is it a reccomendable way to go?
Then, I would like some advices on the lanuages I should use. I am using a linux pc and have understanding in HTML, CSS, PHP, Python, and a bit of JavaScript. Would this be enough?
Can you point me to some useful link/tutorial?
Thanks in advance and sorry if the question is broad, I hope my points are specific enough to be answered without too much pain.
As far as i understand your question, you want to konw about web technologies wich provides you access to camera.
Whrer is an special method, thats returns object in JS, thats can capture camera and mic data:
navigator.getUserMedia()
but it requires sequre protocol https for you server.
You should read about them. In this way, you cat get data from device's camra vai js object, and process, share it as you want.
Related
In my new project with React, I need to implement an environment for designing doors and windows so that the user can design frames through the browser (like the two figures below) and then save it on the server-side. Then I have to fetch and display it in the mobile application that is implemented with React Native. I searched for it but couldn't find anything special that would work. I even found "konvajs" that has done some work in this area but it doesn't work for me and I think I need to develop this feature myself. If you know of any tools or technologies for this, please let me know. If not, what do you think I can do about it?
picture-1
picture-2
After making a duration/cost estimation, I'm about to start developing a desktop application using OpenLayers. I've never had experience on it before, but have the support of some coworkers who do.
Now we have to estimate the time and effort it would take the same application to be viewable in mobile devices. I know the existence of openlayers.mobile.js, but nobody in my company has ever worked with it before.
I know it has some advantages over the normal OpenLayers library, such as pinching for zooming, and so. But, does it has any blocked capabilities? I mean, if I write code to draw a line on a layer in the desktop application, change the simbology of a layer, add a buffer arround a polyline, etc.. will it still work with the mobile library?
Is there funcionality in the desktop version that is not in the mobile one?
I'd need to know before estimating what can I offer in the mobile version, and how hard will it be to get so.
See examples tagged with mobile:
http://dev.openlayers.org/examples/
The next OpenLayer versions will probably have better mobile support as this is something many users are interested in.
Since there are no answers yet, I'm going to rewrite this question in hopes of an answer (I don't mind discussion, but I know SO is about Q&A). It appears security checks/prompts make it unfeasible to use Flash Player. With this in mind, the question still stands, but please answer based on experience using AIR.
I have a Winforms app written in C# that I need to add VOIP to. I really like how well the Flash Player VOIP solution works, the AEC (echo cancel) is awesome. I know they use Speex, but the implementation is still a lot of work even using Speex, so I'd like to use Adobe's solution directly in my app.
Has anyone done this? What issues will I have? A few I can think of:
IPC between AIR and Winforms app. I assume this is easy and several options, including sockets/network, file i/o, maybe others.
Based on this
Content running in the AIR application sandbox does not need the
permission of the user to access the microphone
I don't think security warnings will be an issue? I'm not sure what a sandbox is yet, but as long as my AIR app can run in this and still talk with my winforms app, then shouldn't be an issue.
I assume the voice capture including enhancements (AEC, NS, Speex, etc) are supported in AIR?
Are there any samples I can run that use voice capture in AIR?
I need to build both a website and a mobile site (starting from scratch). The website will include a registration/login, user upload, and sharing feature. I would like to have all of these features available in the mobile site as well. Any recommendations on the best starting approach would be appreciated. For example, should I create the website from start to finish before even starting to think about the mobile site.
Thanks
If you design your server side code correctly, you should be able to use those components no matter where the client is. You would just have to write a thin wrapper for each different interaction type, e.g. xml vs json.
Its hard to say more without knowing exactly what you are doing, and how many people you have working on this? You can finish the desktop version before you start the mobile, but you don't have to. Depending on team size/skill you could develop both concurrently...
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
We're the developers of a relatively complex non-game iPhone 3 application, and we're beginning an ambitious rewrite to take better advantage of iOS 4. There's a significant social element to the app, so we started thinking that we'd like to make it available on as many modern mobile platforms as possible:
iPhone/iOS
Android
Windows Phone
BlackBerry OS
Symbian
There are several approaches to cross-platform development, and they all have limitations. No solution manages to take advantage of all a device's functionality the way a native application can. Given the complexity of our app, I'd simply like to maximize "logical" code reuse without resorting to a cross-platform framework. I'm envisioning tools that will make developing and testing apps against multiple platforms a little more seamless. What can we do to make developing on 5 platforms take less than 5 times the effort?
Push as much of the functionality as you can back to a shared web server, and try to make only the UI specific to the platform.
I know you said no cross-platform frameworks, but perhaps something to look at:
Write all the core logic in javascript. Unit test that at will. Then use tools like Appcelerator to turn that logic into native code.
Then import that logic code into your native platform projects for each of those platforms, and build out the other features you feel can't be achieved properly in any other way.
For platforms they don't support right now, you might be able to find a js to native code converter, or indeed a way of hosting a js environment within those platforms.
None of these will play nice together. It's not in their perceived best interest to do so.
The best bet is to dumb everything down and keep it simple. Simplicity always wins when you are trying to sandbox multiple hostile interests.
Look to XML for all data, and then have 5 binaries to read it or push it all to a web server via PHP. All these mobile platforms will function nicely with XML because it's in their best interest to do so. Worry about branding and appearances AFTER you get the core functionality off the ground.
NOTE: Javascript is the last thing you should be looking at in the beginning. It rarely plays nicely on all platforms in the same way. So make sure that your JS layer is independent of your data layer. DO NOT INTEGRATE THEM. That would be bad. You want your Android JS to be potentially different than the JS you push on the Blackberry for example. Because you won't know how quirky it will end up being until you try it out and test your methods.
I agree with Beth. I have developed a product based on the same thought process. I have a java server running on a socket, which has a client library that client app's use to connect to the server. The client abstracts out the socket piece and provides easy api's for client apps to call.
The server is equipped to handle multiple client connections in parallel, thread pool concept.
Now, since it will be a java client library, you can only run this on android. To get this working on other platforms, you can run this client piece on J2EE. This way you create a third middle layer. All other platforms can then connect using the browser.
With this done, you can now use JSON to Object libraries to expose your object (on the server side) to JSON. I haven't done this yet, but will do it in a few weeks.
Btw, I just cant get myself to use any cross platform frameworks. They promise the world, and dont mention any of their limitations upfront. Its painful towards the end of your product/app release to find out all these limitations/hidden costs.
Well, you can look at JQTouch, SensaTouch or maybe wait for a while to see the jqueryformobile to finally get published. If you are not in a hurry, I would already start working in jQuery, since two out of three from this list are (will be) based on jQuery as plugins
I'm currently thinking to this problem , and my solution would be to put all the logic server side and use an approach like Model-View-Presentation, a series of events fired by the UI that should instead be specific for the client