I recently had my app certified (first time!) but not automatically published. The game is Easter themed and hence I'd like it to appear in the new list over the Easter period. I need to know how best to achieve this.
According to many posts online, the 'new list' isn't sorted in order of release date but instead, in order of certification date, an automated system, the certifiers choice etc.
Thre are some theories here:
http://forums.create.msdn.com/forums/t/85466.aspx
https://stackoverflow.com/questions/6536557/first-time-game-shows-up-way-down-the-list-of-new-free-games-on-wp7-marketplace
Both of these posts are in 2011 and aren't conclusive.
Does anybody know what ACTUALLY happens?
Thank you for any reply.
In my experience, the new apps are changed once per day or in a similar fashion. Again, from experience, you can't do anything to ensure that your application is first. However, I have manually published applications after they have been tested and approved and they were listed in the 'new' category as if they were published that day.
Usually, don't worry because your app will be listed in the first 20 of that 'day' at least once and if you get - or set ;) - some high ratings people will see it.
I found this out the hard way. The plan was to release to a few small markets to get some feedback and then do an update and release to the USA. Well, once the game was released to the USA it was not considered new and did not go into the NEW GAME list. It retained the release date of the initial release to the small markets. And as such, I totally missed out on the new release spike that we all have come to love and enjoy.
Check out Alien Escape
Game Trailer http://www.youtube.com/watch?v=kWE6Dlk6xpc
I have some apps on marketplace already. I can talk from experience. The release after you have published will depend on countries and will delay without fully control. Also if you don't make any advertisement, it will not work with only "keywords on marketplace". I have solved by using my own Webservice and I flagged the app with "LOCKED" view. On EASTERN you can unlock the app by using your Webservice flag and immediately when the app starts, user can use it UNLOCKED.
No other solution is working in time usable way. But I fully like it to have my own app under full control. Also, I have added an "Code behind" for Testers to let them test the app before EASTERN.
Happy eastern
Related
I've been developing a Swift app for a while now on my own individual developer account linked to my longstanding everyday AppleId - so the AppleId also has all my bought music, apps, appleTV and other content etc etc. As I have developed the app I have realised that it has considerable commercial potential, and so would rather release it under an organization (a private limited company) than under my own individual name.
The app itself is relatively straightforward, it is self-contained other than having a single non-consumable in app purchase. I have not yet uploaded the app to AppStoreConnect, although I have set up the app name and the in app purchase on AppStoreConnect for testing purposes. I would like to release in the quickest way possible now. Using XCode 14.
What is the quickest, most straightforward and trouble-free way to achieve my goal? Should I:
Release it under my own individual developer account and then ask apple to change my individual account to an organization account? Are there any complications with this given that this dev account is attached to my personal AppleId? How long does it usually take Apple to achieve the change? Does the App remain on sale throughout? Are there ever any problems or is there anything else I should be aware of?
OR
Set up a totally fresh AppleId and create a new developer account for the organization on this id? (I appreciate this will cost extra money but am willing to bear the cost). If I do this, how do I transfer the app from my individual account to the organization account? Do I have to go through the Apple 'transfer an app' process? Are there any pitfalls with this? When the transfer is complete, how do I alter my XCode set up to continue working on the app under the new account? Also, as I have not yet submitted the app to AppStore (although I have set up the name / IAP ) can I simply use XCode to point the app at the new account and upload it to that instead without invoking the Apple 'transfer an app' process - how would I alter my set up on XCode to achieve this?
I am currently in the process of setting up the company, and should have necessary info eg DUNS no etc fairly shortly.
While I'm familiar with development itself and I've already released one paid app on the AppStore under my own individual account attached to my everyday AppleId, this seemed to be a relatively simple and automated procedure. My main difficulties with my current problem seem to stem from the fact that I have never worked as part of a swift development team, and I understand very little around the actual 'architecture' of app development, eg XCode signing / teams / bundle ids etc, and I'm really struggling to understand the technicalities of the connection between XCode / Developer Account / AppStore Connect / AppleID.
I've looked through other posts on this topic but most seem several years out of date, and I am aware that AppStore functionality in this area has changed over the years.
Any help would be greatly appreciated - particularly if you can recommend which route to go down and answer any of my specific points. I have tried asking Apple, but all I get back are standard replies directing me to their app transfer process - unfortunately though I'm something of a solo outfit and I really need the benefit of people's experience here, as I need this process to go quickly and smoothly!
Cheers!
It's been three weeks since I applied for the release of the app from the Google Play Console.
It is still under review.
This time it's just a minor display improvement, but why is it taking so long?
I've heard that the coronavirus is having an impact, but this time it's too late, and I can't release the iOS app, which has already been reviewed, at the same time.
Is there something wrong with Google right now?
Am I the only one taking this long? How is everyone else doing?
By default, your app will use standard publishing. Certain apps may be subject to extended reviews, which may result in review times of up to 7 days or longer in exceptional cases.
I suggest to talk with chat support to speed up the review process, since you already exceeded the 7 day review period, they will review it manually and publish it
We have uploaded our game app at Google Play successfully. When we tried to upload a second version, we noticed that our app has been restricted in our country. When we investigated we receieved a message from support team stating that the app indicates gambling and that it doesnt match the ranking of "All Ages". We have got a review from IARC stating that we are not having any issues or relation to gambling.
We contacted support again to resolve the issue, but they stated the following:
"The app contain simulated gambling, or games of chance or skill that are conducive to gambling are prohibited in the above locale"
We have done all necessary measures and took the extra mile and change UX to remove any indication to gambling though it doesnt have at the first place. We are suffering from poor communication with support team, and need a super fast fix. Any Recommendations?
Unfortunately this is nearly unsolvable problem, I've faced this and after more than 1 year of appeals with Google I couldn't convince them that my app does not contain any gambling.
Once they flag your app as a gambling app it is very hard to change it.
so released an app a few months ago. It is slowly starting to get more and more installs, not too many until now, it just passed 1000 installations. However, over 90% of new installs are from one country (Germany). It is ranked higher in PlayStore in Germany - but are there any possibilities to increase the reputation in other countries? The app isn't regional, it is an timer for perfect boiled eggs, so interests should not come from only one country... The app is available in English, German, French and Spanish.
Is there a way to increase the reputation and ranking in the Playstore in other countries?
Thanks in advance!
I could suggest something: try promoting your app to other countries through instagram, facebook and see if you get any new installations from the countries you chose. If so then it's not a bug, otherwise you could possibly be facing a bug somewhere in playstore or playstore is not showing your app in other countries.
It is not only about how great your app is but also how people will take it and think of it. Even if your app is available in different languages (English, Spanish, French) which are the most spoken languages, it does not mean that it will have great success. The mindset of the people is different and differs from region to region, what people like and need in Germany does not necessarily be the same in France. Put always the user in the center and understand his needs so you can make the application successful.
There is not official standard dealing with the layout of about boxes, which display the credits of a computer software and other information.
What should a good about box contain? And... is it okay to put an easter egg in?
(source: seasip.info)
I generally prefer to make tabbed "About" boxes. The first tab usually displays information about the application (name, version, copyright, etc.). The other tab is usually a log of changes with the most recent changes at the top.
Legal will want their copyright and stuff, marketing will want their branding (even though the user has already bought the product), the dev team will want their names up there in liquid crystal, but what do users need?
App name and version number. Users may need this to troubleshoot problems, perhaps while in contact with tech support or when using a knowledge base. Use a version number system such that this is all the user needs to specify their build. Version number is also needed for the users to know if they can upgrade.
A brief statement of what the app does (e.g., “Photograph and picture organizer.”). Users often end up with software for which they can’t guess the purpose. “About” is a logical place to tell the user what the app is about.
Put the above in conspicuous text at the top of About. Have a single OK button. Everything else that may be required by others in your company really isn’t of any interest to the user and can all be in “fine print.”
You could also include the web site or email for tech support if you can rely on that being stable for years, but usually users have this before going to the About box.
Easter eggs are fine if you think it’s appropriate to have a little fun in your app and your users lean towards the geeky side of things. Just make sure it isn’t something that will alarm a low-end user (or a future high-end developer; see: http://blogs.msdn.com/jensenh/archive/2005/10/20/483041.aspx).
Looking at a few examples of About boxes:
Name of the software
Name of the publisher/author
Copyright and licensing information
Version information
A nice logo
These days, it probably wouldn't hurt to have a way to directly go to the website for the software in the About box itself.
Microsoft's Windows Vista User Experience Guidelines tend to have useful information on designing good user interfaces. I wasn't able to find information specific to About boxes, but the section for Dialog Boxes may be somewhat relevant.
A team in my workplace actually has made the coolest About box ever:
Every time you open it, it displays a different simple game, with pictures of the dev. team (memory games, tic-tac-toe, sudoku, etc)
As for the About page content, that is the best place to have the version / release information so you can offer easy support.
I am using mine as the abstract description and a link to the legal pages and a credits page. If you have a website, its URL should be there as well -- might as well make that click-able into your own web-view browser to your big "Company About" page on your web server (don't launch a real browser, or the user just left your application).
Make it enjoyable to read but be concise. Avoid any scrolling or paging -- except to a completely different set of informational screens.
Also, let it be obvious and easy to dismiss.
By-the-way, if you add an easter egg to an app that is submitted to Apple Store, you have to disclose the sequence for Apple to 'test'; they promise to keep the sequence confidential. If they discover it later, which will make it back to them through forums, etc., then they will automatically pull it from the store.
I tend to add program name, version, company copyright, contact information, license information. I also add various variables for problem resolving. Winows version, servicepack, dll version if i use critical dll's etc. A large application icon. Sometimes I add an easter egg or some keycombo that launch parts of the program meant for debug and support purposes.