Is anyone aware of any SpeechRecognition framework for iOS that allows using it without predefined Vocabulary?
App I'm making right now is a navigation app, and I want to let my users speak their desired Location and Destination. In this case, making a vocabulary consisting of names of all the cities, towns, villages and streets in the entire US would be a tricky one :)
I made a research and some of the best rated frameworks do not support this feature (OpenEars, Ceed Vocal)
Does anyone knows any that I might missed?
Related
It's called a memory palace (Read: 'Moonwalking with Einstein') it's an ancient tool used to memorize, in my case coding concepts and Spanish and Indonesian phrases.
I'm learning python now, but I'm not really sure what direction to move in and what stack should be used to build a project like this. it wouldn't be too complex, I just want to store and save "text files" in a virtual space like my bedroom or on my favorite hikes.
If anyone has insights or suggestions it'd be much appreciated.
Probably the two most common AR frameworks, on mobile devices anyway, at the moment are ARKit for iOS devices and ARCore for Android devices.
I am sure you can find comparisons of the strengths and weaknesses of each one but it is likely your choice will be determined by the type of device you have.
In either case, it sounds like you want to have 'places' you can return to over time and see your stored content. For this you could build on some common techniques:
link the AR object to some sort of image in the real world and when this image is recognised by the AR app, launch your AR object, in your case a text file.
use 'Cloud Anchors' - these are essentially anchors for AR objects that can persist over time, when you close the app and come back to it later, and even be shared between users on different devices.
You can find more information on cloud Anchors at the link below, including information on using them with iOS and on Android:
https://developers.google.com/ar/develop/java/cloud-anchors/overview-android
We're looking to share AR experiences (ARWorldMap) over the web (not necessarily to devices nearby, I'm referring to data that can be stored to some server and then retrieved by another user).
Right now we're looking into ARWorldMap which is pretty awesome, but I think it only works on the same device AND with devices nearby. We want to be able to delete these constraints (and therefore save the experience over the web on some server) so that everyone else can automatically see 3D things with their devices (not necessarily at the same time) exactly where they were places.
Do you know if it's possible to send the archived data (ARWorldMap) to some server in some kind of format so that another user can later retrieve that data and load the AR experience on their device?
The ARWorldMap contains the feature points in the enviroment around the user. For example, the exact position and size of a table but including all the other points found by the camera. You can visualize those with the debugOptions.
It does not make sense to share those to a user that is not in the same room.
What you want to do is share the interactions between the users, eg when an object was placed or rotated.
This is something you would need to implement yourself anyway since ARWorldMap only contains anchors and features.
I can recommend Inside Swift Shot from last years WWDC as a starting point.
Yep technically it’s possible as according to docs here. You will have to use the nsssecure coding protocol, might have to extend if you aren’t using a swift backend though. It’s still possible as the arkit anchors are defined by a mix of point maps, rotational data , and image algos. Just implement portions of codable to JSON and voila it’s viable for most backends. Of course this is easier said then done.
We already have E commerce app Targeting 3 different countries with 3 different domains. It also uses 3 different DB.
Now we are going for IOS app. So my questions here are:
Can we upload a bundle for specific country only? (Available in that country only, if multiple bundles allowed for single app)
Should we handle JSON based DB request in a single bundle by checking user's location? (so single bundle handled by programming)
Our goal is here our app will allow only specific country's user to place order.
Also prices are different for different countries, prices are from server.
We don't have in app purchase prices.
Please let me know what option is best. Even if new please suggest.
Its a broad question with lots of good answers and unfortunately all of them are opinion based but I will give my two cents.
You can absolutely create multiple apps and target a specific country. You control this by changing the availability preference. (see pic) This will allow the app to be shown only in a certain country.
The advantage of this method is that you can have complete control & customizability specific to a country.
The disadvantage is that you are now maintaining multiple code bases. If you have a code bug in one app then you need to update 3 apps to fix the "same" bug. What if you want to support more countries. Now you have to create that many clones of the app. Think about if you had to add a new feature. Its snowballs pretty quickly doesn't it?
If you make one app then there is only one code base, one place to make all code changes or add features. Its somewhat easy to maintain code wise.
The bad side, well now you have to take care of every possible country specific scenario either within the app e.g. Localizations, currencies etc. or you have to get that information from your servers.
There are ways to find out through apis from which country a user is connecting from without asking the user itself.
In my opinion, creating one app is the way to go. It will save you lots of headaches down the road. But having said that I don't know how UBER or others big international players handle their country specific apps. Do they have one app or many. That I don't know.
I am working on a navigation app that utilizes voice recognition to point the user towards their destination. However, this may require phrases or words outside what might be obvious. "Navigate to" would be simple, since I can add it to the dictionary, but "starbucks" won't be so easy. I could simply add starbucks, but that only solves one venue out of the hundreds of thousands that have non-standard names. I am looking for a way to do this in a more widespread way.
Is there any way to setup or configure Openears to detect and understand all words said?
I'm trying to make an application that is a map of my High School, in which the user can click a button to search for either a room or a locker.... My goal was to have the room/locker number correspond to a point on several hidden "number lines" in different areas on the Nib file/display, and when a certain input is received, the corresponding number would light up or show its location (i.e. I don't have to enter every locker location for instance, only the first and last one in each hallway, and the number line generated between the values I enter would represent all the lockers in-between).
I'm using Xcode 4.3.3 if that helps.... Structure-wise I wanted to use the Tabbed-application template and have one tab for the actual Map, one for entering which locker you are looking for, and one for entering which room you want to find. I'm new to iOS programming so I don't know if there is a better way to accomplish something like this, and I am open to any suggestions or advice. Thanks!
You could marry MapKit with your own database in which you'd define the coordinates for rooms, banks of lockers, etc. See Location Awareness Programming Guide which shows how to integrate maps in an app. I can imagine that you could define MKOverlay objects for rooms and ranges of lockers. Or you could simply define MKAnnotation objects for points of interest (cafeteria, etc.).
But some combination of overlays and annotations using MapKit seems like a logical solution.
You might also use the MapBox iOS SDK to do this, along with an interactivity layer as described at http://mapbox.com/tilemill/docs/crashcourse/tooltips/