One IOS App, 3 countries domain using 3 different Data bases - ios

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.

Related

How promote the application in AppStrore?

I’m making an application for iOS, I plan to release it in the App Store soon. The question arose - how to promote it correctly? Catch up with the audience? How to form the content initially, given that the application is something like a message board, respectively, if people download it, but it is empty, it does not fit. And is it better to launch it first in one city or in several? If anyone has such experience, I will be very grateful for the advice and answers.
The App Store
Apple’s App Store is a vast and complex ecosystem containing millions of apps across dozens of categories. But this vast selection is only valuable if users are able to find the apps they’re looking for. To that end, Apple has designed the App Store to promote discoverability.
How do people discover apps?
There are two main ways users discover apps in the App Store: by searching for keywords and by browsing featured and top charts. Surveys have shown that between 20 and 50% of users find apps by search, while another 14 to 20% discover them by browsing categories or looking at Apple’s featured selections.
App name and keywords
According to Apple, nearly ⅔ of app downloads result from searching. Therefore, it’s worth spending some time thinking about how to optimize your app for search. Your app’s search relevance is determined mostly by your app name and keywords, so let’s take a look at each of those in turn.
Apple once permitted app names to be more than 200 characters, leading to “names” that were chock full of SEO-gaming keywords, metadata, and the names of rival apps. Today, App Store guidelines limit developers to 50 characters and prohibit terms and descriptions that are not the name of the app.
When it comes to keywords, developers are limited to just 100 characters per app. With so few characters to work with, developers need a deliberate strategy. Ask yourself: What keywords are most important to you, and what are the keywords that will set you apart from your competitors? The best keywords are both relevant to your app and frequently searched, but the former outweighs the latter.
Remember: Users are much more likely to go with the top search results. Therefore, it’s generally better to be ranked #2 or #4 for a keyword that’s searched fifty-thousand times a month than to only be ranked #345 for a keyword that’s searched a million times a month.
Lastly, some brass tacks:
Separate keywords with commas.
Break down phrases into individual words (i.e., “photo, editor” not “photo editor”)
Save characters by not pluralizing your keywords (i.e., “calendar” not “calendars”)
Getting featured
Getting an app featured in the App Store is the dream of many developers. Not only does it confer special recognition on your app, it also gets you more prominent placement in the App Store. To add icing to the cake, getting featured also permits app developers to customize both their app and developer pages, further enabling them to stand out from the crowd.
A survey by Applause found that 40% of awareness of apps comes from browsing the App Store. In raw terms, that means getting featured on one of the dozens of lists, which are themselves created by a combination of popularity and editorial curation by Apple. Since users in general are more likely to trust (and therefore download) an app that they’re already aware of, having a recognized presence in the App Store is a major asset.
So how do you get your app into this elite group?
Obviously, there’s no substitute for quality. The best way to get an app featured is simply to build a great app. Apple’s curators are always looking for new apps that their users will be excited about. To that point, having a world class user experience goes a long way.
Beyond that, it helps to understand how the App Store works. A former App Store manager has revealed that the App Store isn’t a monolithic app supermarket, like Walmart or Target, it’s actually more like a bustling mall with dozens of small stores specializing in different areas. Each of these editorial teams is dedicated to a specific category or region, and each makes its decisions about what apps to feature internally. That said, developers can pitch their apps to Apple’s marketing team, who may then choose to advocate for an app within Apple. Going to events like WWDC and chatting up Apple representatives can also be a good way to raise awareness inside Apple about your work, especially if you’re a small or first-time developer.
Another thing that Apple’s editorial teams consider when choosing what apps to feature is whether an app takes advantage of Apple’s newest and most exciting tech. Remember, promoting an app in the App Store is also about promoting features that set iOS apart. Taking advantage of the newest APIs and functionalities can make your app more timely and relevant when Apple is choosing what apps to feature.
App Store search ads
A relatively new product from Apple allows developers to promote their app at the top of search results. Given that nearly ⅔ of app downloads come from searching, Search Ads can be an effective way to give an app the bump it needs to get found.
Search Ads are built around an automated auction process similar to Google AdWords. Developers set a maximum price they’re willing to spend per tap, which is then compared against the bid of the next most relevant competitor. Developers only pay when a user engages with one of their ads.
As with organic search results, relevance is the main determinant for whether an app is likely to appear on a given page of results, not how much a developer is willing to pay for placement. Relevance is determined by a combination of App Store metadata and user response.
That’s just a broad overview. Search Ads also includes some advanced features, like the ability to target specific groups based on demographic and location data. It also includes services to help you target your ad spend by recommending keywords based on your app’s metadata.
However you promote your app, it’s important to make sure you’re doing it in a cost-effective way. Marketing analysts and SEO experts may be able to help you optimize your marketing spend to ensure that your app gets in front of the right users based on your business objectives.

iPhone app with Territory Limitation

Currently I have a live iPhone app. I need to convert it to a paid one with territory limitations. That means I need to make my app paid for some territories and free for the rest.
Will apple allow this?
Can I upload 2 separate apps with same features, one is free and other is paid but their no feature changes. Only territory limitations.
First thing is you can not change price of the same Application for different territory. Apple will not allow to do so. In fact there is no such option to set different price for different territory.
So for the second you mentioned i say YES. To do so you to keep few things in mind.
Let say you have created 2 different applications with same features for 2 different countries with different price tags
Make sure the version which you uploaded for Country-A should be only visible to Country-A. And same for Country-B.
Keep Description & keywords localized language.
Make sure there is something different in both app versions. Otherwise Apple team will feel its a similar concept & they might reject the application.
Hope it will guide you.

A/B testing(show new feature only for 50% of users)

I'am creating a new feature for my iOS app. After I publish the app I wants to show the new feature only for 50% of the users, so I can do some testing which version makes more orders. I have no idea how to do it without using some third parties like Optimizely.
Also is it possible to do this using Google Tag Manager(GTM).
So can someone please help me to figure this out.
Thank you very much for your time.:)
It’s hard to do it on your own, though not impossible of course: Optimizelys of the world are just programs. You’ll need to solve these problems:
Targeting: Some algorithm that will assign user session to either control or (one of) treatment(s). This has to be random, of course, or you may as well stop there.
Routing: Send sessios to the targeted experience.
Logging: You’ll need to intelligently log events from sessions as they traverse their targeted experience. These may be many, so be careful not to add latency to your app path. Your statistical analysis will be based on these.
Experience stability: how do you ensure (if you do) that a returning user sees the same experience he’s already seen.
Note as well, that Optimizely will only help you if all your changes are on the device and not on the server. If you need to instrument server changes as well, you’ll have to look into Sitespect or Variant.
I finally figured out how to do the A/B testing with 'Google Tag Manager'(GTM).
In GTM you can create a variable called 'Google Analytics Content Experiment'. With this variable you can select how many percentage of users going to see each Variation(your experiments). You can create up to 10 variations for single experiment.
GTM is so cool and powerful. GTM contains so many features that could save lot of time and I totally recommend it for anyone who is going to do A/B testing.

Is an iOS App Store promo code usable by multiple people, or just one per code?

Is it possible to generate a single promo code which can be used multiple times by multiple users, or is there a one-to-one mapping between codes and specific users?
What I'd like to do is publicly post a single code anyone can use.
Is this possible?
The promo codes are one use only. The person using it is buying your app but without paying any money to Apple. You could lower the price of your app to free for a limited time if you wanted.

Creating PDFs from iOS text fields

I'm working on the requirements & specifications for a new iOS app intended for use by certain professionals working "in the field". All day long for weeks on end, these folks have a sizable reporting burden to their superiors using standardized forms that track all different kinds of information. Traditionally, those forms are in PDF, and are simply printed and filled out in ink and then shared with the dozens to hundreds of others working the same operation. Sometimes they'll use a PDF with form fields so the data can be typed and then printed as part of the form. Either way, given their workflow, time and stress pressures, and other factors, it's not a very productive way to get the standardized reporting forms done.
The app we're spec'ing would offer an iOS (and Android, if possible -- but secondary or even tertiary requirement at this point) user interface for tracking the data they enter in the field, organizing it in a logical manner for each individual user, and with the press of a button, take all that data and automatically create a PDF file of it using the standardized form.
Of course, the forms are STRICTLY and rigidly standardized in this industry, and any deviation in format, structure, or presentation is simply not tolerable.
So I was approaching the project by thinking the app would maintain an internal repository of the original standardized forms from the accrediting organization, with each possible data area defined as a field. The app would:
open the necessary PDF form for the task at hand;
parse its dictionary to identity the specific data fields;
for every single field, identify the relevant data from the iOS app's own user interface and data tables, and assign that data to the corresponding field from the PDF/dictionary
export the PDF to a NEW PDF file, which the app would either email or store through iCloud, Dropbox, or some other form of file sharing.
The catch with #4 is that that PDF file must remain editable by standard PDF applications on Windows and Mac (Acrobat, Preview, etc.), so all the fields need to remain. And the PDF should be viewable just the same on either Windows or Mac.
Now, at NO time will the PDF (neither the original nor the exported final document) EVER need to be displayed inside the iOS app, nor would it make much sense to be able to do so.
I don't know if any of this is possible. This is our first iOS project, and we've been leaning towards building the app using Moai or Corona or some other framework to save development time and make porting across platforms easier. That said, if it cannot be done using Lua and one of these frameworks (I remain skeptical...they seem HIGHLY geared towards games), we're not opposed to doing it directly in Objective C and building an Android version some time down the road.
But either way, I'm at a loss in assessing whether this is even a practical undertaking. Our requirements are clear, and frankly if this can't be done, the project won't be pursued any further. But I could definitely use some help from you folks in identifying what my options are, whether I can do it in Lua, and what SDK(s) would be most useful in accomplishing this.
Based on what you've said, it seems that there is little reason to do the PDF-based part of the work on the mobile device itself since:
you don't need to display it on the ipad
you plan to email it or store it in the cloud
if you write this for iOS you will have to write again for Android as you've mentioned
Can you simplify the mobile part of your requirement by focusing on the data-collection and validation, then firing off to a server to do the document production? That will give you a lot more flexibility in the tools that you can use to merge the data into PDF docs. If so you could look at creating PDFs or populating the fields from code using something like iText (C# or Java). If you don't want to build your own back end server you could try something like Docmosis Cloud - but that might not allow you to get your precise layouts.
Certainly the catch you mentioned - needing to keep the PDFs editable with their fields is a significant gotcha in all cases. If you could convince the stakeholders that it is better to generate the final documents from your system (generate draft, review, update data, generate again etc) - rather than generating editable documents that you then lose control and tracability over, then you will be miles ahead.
Hope that helps.
Did you consider just generating a new pdf using an image of the form as the background to the pdf and just writing the user's data into the required areas over the form image. Would reduce the complexity of trying to parse the original form PDFs.
That's a point of worthwhile discussion, but one we don't have an ideal answer on. I tend to think of that as the almost perfect scenario -- it'd be considerably easier to develop. There are two key issues with this approach that have made us table it except as a very last resort:
The users of this product would be working in the field. That field could be quite literally anywhere--the streets of Manhattan, a disaster-stricken area with infrastructure that's been severely damaged or even destroyed, or the most war-ravaged third world country. If it were the streets of, say, Manhattan, there's no problem--their iOS or Android device will have 3G or Wi-Fi access just about anywhere they go. In the latter two scenarios (which are arguably more common in this industry), that connectivity may be very limited. The concern is whether the end user's ability to be productive or to see and share data with their colleagues will be too greatly restricted if they don't have a decent signal. To be fair though, even today they often aren't even using mobile devices, forcing them to go back to a headquarters type location or use radios to share information, effectively negating my point here. But if we're not going to significantly increase their productivity in the field, it just gives us pause to think through whether or not we have enough of a value proposition to ask them to fairly significantly change their methods of doing things.
To your latter point, no there's no convincing the stakeholders that this new system is the better approach. Even if there were, it would take years to do so. These forms are a part of a well-defined, decades-old standard used by literally thousands of organizations.

Resources