When someone comes to my app's page on Apple's App Store, right now they see the sections in this order:
Version Information/What's New Section
Description Section
Is there a way to swap the two sections? I want visitors to my app store page to immediately see the Description of my app, followed by the What's New section, not vice versa.
This might be a very basic question but I could not find any helpful articles online and appreciate the help!
The (Mac) App Store layout is determined and managed by Apple. There is no way for you to change any of the order of the elements.
Related
I have a very simple application, and i want to add into it a database. For all of you, to understand what i mean, it should look similar like default application "Contacts" in iPhone. It should contain list of elements (like people names in contact list), and when the user click name, the next view appear, which contain information about contact (and other buttons as well). All of data must be inside of application (not downloading from web pages).
Please help me! I am novice, and i have no clue what i should looking for, not just an array i guess... i will gratefully accept any of advice and links to examples, related to my problem.
PS. My app is not about contacts, its about diet. For example, it should look like: user click element "cheese" in list, and then next view provide information about product (calories, protein, fat etc.)
Take a look at the following free lessons from iTunes U. Paul Hegarty is an excellent teacher. These are dense so I had to watch a couple times, but everything you need is here:
Basic Persistence:
http://www.stanford.edu/class/cs193p/cgi-bin/drupal/node/285
Core Data (Lecture):
http://www.stanford.edu/class/cs193p/cgi-bin/drupal/node/287
Core Data Demo:
http://www.stanford.edu/class/cs193p/cgi-bin/drupal/node/289
These pages have the pdfs, but go to iTunes and download the full lectures for an excellent overview. Also don't miss the CoreDataTableViewController available on the last linked page - handy.
Without this course I would not be an iOS developer, so I can't recommend it highly enough.
Enjoy,
Damien
Sorry for this basic question but all attempts at Googling and using facebook help only provide out of date information.
I am attempting to make my first fb app. Just an html page saying hello. From what I understand the app (or webpage) is stored on my server and I set up a facebook app that basically points to the URL of the app (or webpage) on my server.
Is this basically correct.
Where do I enter this URL information in my edit app screen. I have followed the latest fb instructions and all I see when I view the app is the admin page in fb for the app.
Does it take a long time for the page to appear.
Is there a current idiots guide. The app design is not a problem for me loading it in to facebook is the problem.
Unfortunately this wasn't very helpful, not because of what you posted but due to the fact that it appears that Facebook has updated the way in which pages are linked to again.
The pages you suggested I look at were well laid out with lots of information on them but they are already out of date and do not seem to correspond with the layout of the Facebook 'dev app' and even the fields in the form seem to have been either dropped added to renamed.
Thanks for trying to help me and I hope that FB may produce some up to date information soon and not keep changing the interface.
I can completely understand your confusion - the Facebook docs give very little information for the complete beginner. The 'Getting Started' section makes some massive assumptions and completely ignores huge key areas you need to know to get your first application up and running.
So to address your points:
Yes, this is basically correct. Apps on Facebook are served up to the user in one of two ways. Either as a 'Canvas App' or a 'Tab App'. A Tab App is an application you can install as a tab on a profile page. A Canvas App can operate on it's own page and has more room as there's no left menu as you would have on a profile page. You can configure a single app to work in both ways.
To edit your application settings, go to your own Facebook home page. Use the search bar to search for the 'Developer App'. Typing in 'developer' should do it - it should be the first result in the App section with around 830,000 monthly users. This Developer app is the window into your own app settings. You need to install it if you haven't already. It's a hub where all the apps you create will be available for you to edit. Whenever you want to edit one of your app settings in future, you click the Developer bookmark that will now be in the left menu on your own Facebook home page.
No. Apps are basically an iframe onto your code. There should be very little if any wait at all. Start with something very simple like spitting out some straight html so you can easily tell if things are set up correctly.
Yes. I found thinkdiff.net to be massively useful in the early days to get my head round the basics and then more advanced concepts. There's tons of examples ranging from very simple to quite advanced. I've just had a quick look around and found this page which should give you a decent head start in getting things moving. Note: I have no affiliation with thinkdiff.net at all - I just found them helpful in the past.
Finally, a request from me; this whole stack overflow thing is new for Facebook developers and very few people are voting up answers they consider helpful. This means new users to SO but experienced FB developers can't vote up good answers and vote down bad ones as we need enough Reputation Points to do so. If this has helped you, please ensure you vote up the answer. Of course if it was rubbish and you're just as lost, dont :D
Hope I've helped in some small way; I know I was completely lost for the first few weeks with FB development and even now there are things that make me tear my hair out! In the end it's very rewarding, but you have to put in the time. Good luck :)
I'm currently working on an iPhone project where i want to present to the user spesific terms from wikipedia. I'm facing tow difficulties right now:
1. I want the specific content to work offline.
2. I want to show the relevant pictures as well.
I need to find the most efficient way to do it, can someone advise ?
You could get the content online and cache them in the app DB. If necessary you could prepolutate the db directly in you app. That way some terms would already be available.
I am making an app for an author (Patrick Rothfuss) and I would like to be able to link to his book in the iTunes store by clicking a UI button. While I think I can set up the button and everything myself, I can't seem to find out what the link is.
Anyone have any idea how to do this?
Thanks
For a more official approach from Apple, see iTunes Link Maker to generate links for iBooks as well as apps and everything else.
It seems that it is still limited to making country-specific links. But you can delete the country part and it would still work.
As example:
https://itunes.apple.com/us/book/moby-dick/id498469635?mt=11&uo=4
Can be also written as (and work on every country):
https://itunes.apple.com/book/id498469635?mt=11&uo=4
We have deleted book name "moby-dick" (recommended because it's subject to change sometimes) and also the country data "us".
I think currently its undocumented by Apple, but might be they provide the custom url of iBook in near future.
We we wondering what are some ways developers have added a help function to their apps. What are some techniques people have used?
One way we were thinking of is to us UIWebView to display a HTML file with help instructions.
Thoughts appreciated.
I'm using UIWebView right now which pretty much contains all the help in a single page, along with some JQuery things to display popups, etc. But I like the way iCab Mobile (et al.) are doing things which is a sectioned UITableView with each row a separate topic or section within their overall help information (complete with icons...) then in their bundle they have each section in its own html file, organized by localization.
Another thing in my queue for the next release is to provide a dynamic "News" view. The rough idea is as follows... I have on my server a file or CGI where I can place small bits of news I'd like to push out to users. On startup, my app checks for network availability and if present, start a thread to see if anything has changed on the server since last updating the News data. If changes present, post an alert letting user know, and asking if they'd like to read it now. At that point, the latest news is already downloaded and cached, so they can simply read it later if they want, and I won't post anymore alerts until the server file changes again. (And one could add a preference/setting to disable these alerts.)
I'm thinking this would be a good way to let people know that some nasty bug is known and fixed and an update is sitting in the queue, solicit beta testers, promote upcoming features or other apps, etc. I can see where constant alerts everytime I've got something new to promote would get annoying, so having a setting to disable them means the user never has to read them unless they want to. Although some kind of override to warn of recently discovered/fixed bugs seems sensible.
FWIW, the author of Mover+/Mover has just started doing a similar thing, though I think Emanuele is perhaps only showing one Notelet at a time, whereas I envision a bit more of a history (shown in UIWebView) until I decide to age stuff off the bottom of the stack.
I'm using a scroll/page view to show several images containing small notes. Each image then tells the user about the more advanced functions on a specific part of the app.
In my opinion the help should only contain information that isn't a 100% relevant for the use of the application. It should be things the advanced user should use to make more use of the app. It should contain gold for the power users. The "basics" should be so obvious that no help would ever be needed. If that's not the case, I think, you've failed as a developer on the iPhone platform.
(Here's a screen shot from my demo app)
I'm currently creating a fairly complicated app. I'm thinking of doing help as a semi-transparent overlay - help in text form is hard to swallow for users; it's much more helpful to just point at stuff and say "this does that".