I created a project, settings its name, say: ABCXYZ. When I use iOS Search app (swipe down in the main menu), type XYZ, my app doesn't appear.
What do I have to include in my XCode project in order to get more option in search? Like, type A, type X, they show my App. In case of ABC-XYZ also.
Additional, I want user can search our company name also. Like Company1, they search Company1 and show our company's apps (in this case is ABCXYZ).
You can't do much about it since the spotlight's search mechanism is built-in in iOS. When user types a keyword, iOS will search the following two names of all installed apps:
The app's bundle display name (the name used in your home screen).
The (usually) longer name used in the App Store.
When searching, iOS will do a case-insensitive match from the beginning of each "word" in the name. For example, if your app is called ABCXYZ, both A, ABC and ABCX will match the name, but not XYZ. However, it's worth pointing out that each "component" of the camel-case styled name will be treated as a different word. So if your app is named AbcXyz, keyword of abc and xyz will both match your app.
AFAIK there is no way to alter the search mechanism or add new keywords to your app. All you can do is to optimize the aforementioned two names that are used for searching. For example, you can include some relevant information in your "App Store name," but I wouldn't recommend to abuse it.
Related
It is possible to register one (Delphi) app for multiple uses, with more than one icon in App Chooser? For instance like this:
register app to open some file types (I know how to do that)
register to open/acces to any file, but App Chooser should show icon different than main app icon, and different text, not the app name - for instance "Base 64 encode/decode file"
same thing, for text files or other documents/images compatible with operation - "Convert to pdf"
All functionality is built in the same app, but operation, and icon in the App Choser, should depend of parameter passed in intent, as EXTRA_TEXT for instance. For instance, if EXTRA_TEXT is "b64enc" the app should auto encode the file on intent EncodedPath, then save base 64 encoded file in app documents folder, notify user "conversion complete", then close itself.
For example, app can use file extension to choose what to do with the file, but this is not enough for functionality I need.
I have seen this answer
Multiple Application Files in one Android app
and it is OK as some kind of guidance, but not really an answer on this question :-)
In Windows the same application can register itself in Win context menu for multiple purposes with different icons and different context menu text, and same program can do different operations on the file, depends on parameter passed to the program.
So, it is possible in Android, maybe via AndroidManifest, or I shoud use different approach? And if I must, is it possible to have multiple activities in Delphi app for Android?
Edit: I have found this blog
https://blog.andreamagni.eu/2019/02/how-to-add-android-app-shortcuts-to-a-fmx-application/
and looks like maybe it is possible by using shortcuts
I understand that if the app name contains spacing, then when we append the app name to Core Data entity class name, we need to replace the spaces with underscores e.g. My Game with My_Game.
What if the app name contains exclamation mark i.e. ! or ? how does this effect the application name?
Bluehound made the best point of all, that core data models and project names shouldn't contain crazy characters (which Xcode and MacOS might not deal predictably with). The place to add your exclamation points and/or those crazy characters is in the app's Info.plist file, which is where the display name is set via the "CFBundleDisplayName".
How do to this can be found in this tutorial.
We're currently at the stage of looking at localising our app in to multiple languages now that the general concepts of the app have been decided. This is something I want to ensure is done correct from the start to lower the risk of headaches in the future.
The app targets iOS 7 and above, uses storyboards, and is written in Swift.
Storyboards
When working with a storyboard (or a xib), what's the best way to mark a UI element as "not to be translated"? For example, I have a placeholder string for a user's display name (Display Name), which will be replaced by a users display name at run time. This display name will not be localised, but neither should the string "Display Name". Is there a method of not having a UI element's value automatically put in to the strings file? If not, is going in to that file and manually removing strings I don't want localising a sustainable option?
Strings In Code
I'm using the Swift function NSLocalizedString with the key and comment parameters. Some places I've seen say to set the key to be a unique id based on the context (e.g., intro.login-button-text), while others seem to just put the full string in the default language (e.g., Login). I like the idea of the unique ids for the key, but would this not go against the idea of the "base" language?
Exporting
Xcode 6's "Export For Localization" option seems very useful for getting the correct format of file to be sent to translators. However, as mentioned previously, placeholder text does not need to be translated. Should these placeholders be removed from the exported xliff or the strings file prior to export?
Looking for the the same questions myself. Hope this will help you and others. Also I would recommend to have some kind of tool to organize the xliff/string files
Storyboards:
I've seen developers putting non translating texts in storyboard with extra parentheses. i.e. {Display name}.
By using this you can see by the translation itself if it needs to be translated or not. We use oneskyapp.com and can select to hide those translations and they will be hidden for each import of that key.
Strings in Code
By following this thread they suggest to use keywords.
Best practice for key values in translation files
Exporting
I cannot find a way to have some translations automatically removed when exporting. Off course you can put the views which has dynamic fields in different XIB/storyboards and decide not to translate those.
Again a tool like onskyapp.com can help you with this.
Formats
As of context with the field is important and a translation can be different when it is followed by i.e. a users name I would go for "%1$# is online!"
I wrote a game with cocos2d and translated all the image and text in the
game in two different language.
When the app launches, I load different resource according to the locale of
the device and this worked all OK.
Then when I upload this app for review, I first named it say "test".
Then in the localization part I add a language "Japanese".
But I found that in the "Japanese meta data part", I can edit a lot of
things except the "app name" which is "test". But I want my app to show
different names according to the locale of the device also.
Can somebody tell me how to get this work? Thanks in advance...
You can create a file called InfoPlist.strings in each of your language specific directories, and set a language specific value for CFBundleDisplayName.
How do I get an existing Document Type to show up in the Create dialogue of Umbraco 4.
I installed the BlogForUmbraco4_1.0.0 package, which I realize tries to install as the primary site, but it also installs all of the necessary Document Types, including Blog, and BlogPost. Why are they not an option when creating a new item within my site.
Umbraco uses a permission based Document Type Hierarchy, to ensure that editors doesn't create weird page types in wrong places (like a 'Homepage' beneath a blog or a 'News Item' inside a Gallery).
So you'll need to allow the Document Type that you wish to appear in your create dialog to the Document Type of the page you're using as the parent (this might sound like non sense ;-)).
So, say that you've imported the Blog4Umbraco package and wants to allow a blog below a Home page, you should find out which Document Type that home page is (look at the properties tab on the document and look at the 'Document Type').
Go to settings section and open Document types and click on that doc type (let's just say it's called 'Homepage')
Click on the 'Structure' tab and you'll see a list of all Document Types in your install. Some of them are already checked and those are the ones that are allowed beneath that type. To allow blogs, simply check the 'Blog' document type as well :-)