Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
Note: This question IS programming related! It's all about better code and better software concepts through reading what customers say! So please don't close this, as it's important for my (and probably also your) software projects.
In order to write great software, it is essential to read reviews of apps from competitors. That way, you can see what they did wrong and improve on it.
BUT: Apple jails every country into it's own tiny bubble. It's almost impossible to read reviews of users from outside your country. Sometimes, when I'm lucky, Google does return an iTunes website with an app in english and I can read english reviews from people in the US. But most of the times, I end up beeing redirected to iTunes or the App Store app, launching my tiny and insignificant German bubble of some few reviews.
It's ridiculous that these days where the world should be open to everyone, someone like Apple restricts the people to their own countries.
Does anyone have a good advice how to break out from this jail of artificial content witholding? I don't live in China, so I don't want to be threated like if I would. I want to read your US reviews, your French reviews, and even your Pakistani reviews.
I want to make better apps, but I can't if 95% of worldwide reviews are hidden from me as an developer.
Have a look at AppReviewsFinder - small but handy Java application for grabbing customer reviews and ratings from app stores.
At the bottom right of the iTunes web site, there's an round button with the flag of your country. With that button, you can switch the country. I don't know if you can switch to any country.
There's a similar functionality in the iTunes application.
That's the best approach I know. I'd be glad if there was something more useful and less cumbersome.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
My client's application is rejected by apple which I have developed, he sent me not enough information but he just sent me reference number on apple review guide line 2.5 which says "Apps that use non-public APIs will be rejected", I checked external APIs on my project but all of them public except Native CSS which I don't have idea that whether apple accept this or not. My application is not very big its a small project. I also asked the client to send me detail info so that I can sniff in better way. If any one has idea about native css please guide me. Thanks
Apple does not reject an application because the user interface is built using HTML. In fact, many Apple apps or advertising platforms for iOS are entirely built with HTML, CSS, and JavaScript. For instance, the Apple Store and iAd advertising platform, among others, use HTML as the primary medium for the user interface. Outside of Apple there are many successful apps that have user interfaces built with HTML, including LinkedIn, Wikipedia, the BBC Olympics, and many, many others.
Apple rejects applications that do not:
have a user experience that feels like an "app"
feel "at home" in the iOS ecosystem
offer a differentiation from a mobile web experience
This applies to all apps, not just apps developed using HTML for the UI. Adobe is not Apple, so we do not know the exact approval rules beyond the "App Review Guidelines" and "App Store Review Guidelines" provided by Apple. However, it is clear that approval largely comes down to the user experience: how the user interacts with the app and how it "feels" on the device.
know more about this from Dealing with apple app rejection
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
With so many tools and technologies lying around, I am looking for suggestions around the best ones (UI/server-side frameworks/database/CMS) to use for building a web(site/app) similar to Facebook itself.
Details of the website cannot be revealed due to privacy concerns. But largely, the experience and interactions would be similar to what Facebook has (such as continuous feeds, groups, upload data/files, comments, etc.), just that it would be in a different domain.
Information (or links) on what technologies/frameworks are such sites/portals using will also be of great help!
Elgg is a great start. they have numerous plugins (some that even make it look very similar to facebook). I've seen some prototypes that where built in a few days that have tons of functionality
The simple answer is PHP. But people likely imagine a LAMP stack.
Facebook has reengineered the front side and back side of PHP, as I understand it. They use the HipHop compiler to cut the cost of execution of PHP. And I don't know the details, but they have some kind of backside distributed database they use instead of PHP/LAMP traditional use of MySQL.
(See http://www.facebook.com/note.php?note_id=24413138919 for a description of one of the mechanisms they use, Cassandra).
If you don't care about scale, you can skip these two steps and save a lot of engineering.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 4 years ago.
Improve this question
I am thinking of putting together an app that will be pulling data from a very popular website. I have already looked at search and responses from the site and believe it can be done.
The only one question I have is, will apple have a problem with me doing this? The website more than likely will NOT give me permission to skim, but its public information so.... Will apple reject my app because I am skimming another site for data?
I would setup my own server to do the skimming but I am sure this website will see my ip hitting their servers a billion time a day (hopefully :) and ban my ip, so I plan on having the iphone itself skim the site.
Apple probably won't have an issue with this, but the website probably will. Most websites hate scrapers and put it in their terms of service that you're not allowed to scrape.
Apple only reject apps like this if they scrape Apple websites. Apple aren't bothered if you scrape someone else's site.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I've created an app, that is self-explanatory. What is the etiquette in the iPhone world: do I still need to have an About button that explains what the app does, website, email, all that? Or is that unnecessary?
I wouldn't consider it necessary, but then again I would get a second opinion about your app being self-explanatory; you wrote it after all :) Seriously, I've found a lot of "obvious" UI and behavior I've written over the years to be not so, and it's helped to have opinions from others (especially those who don't use computers for day-to-day work) to bring more clarity.
But from an etiquette standpoint, I'd say no: in fact if your app truly is self-explanatory it'll just get in the way of what your app does, which is what consumers are after.
I think that you almost always need one, especially in a paid application. You want it to be as easy as possible for your users to get in contact with you for support (no need to make an upset user angrier by making them search for your contact info), because happy users leave good reviews, and support requests often help you to figure out what needs work in your app. Additionally, if you release a free app but you also have some paid apps for sale, I think the free apps need an about screen that will send your users to your page on the App Store; after all, you might as well get some free, non-invasive promotion when giving away something.
The only time you probably don't want to include an about screen is when you don't want to hear from users. If you're giving away a free app, and you don't want to deal with people having problems with it, then don't even bother with an about box. Or if you're Apple, since about boxes in their apps would be redundant.
I don't entirely agree with zoul here. I think that every app should include information about how to contact the developer and/or get support if it's needed. Yes, you can put this information in the App Store listing, but that makes it more difficult for your customer. I'd say yes, add the About view.
The etiquette in the iPhone world is to design sane applications. If your application does not need an About screen, don’t do it. Those who want support can always check out your application description in the App Store.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
I'd like to build an app that uses voice recognition. I've seen big companies like Google etc implement this feature, but I'm curious about doing it on a start-up level. Anyone looked into this? Are there any tools out there for us to do this?
OpenEars looks promising...
http://www.politepix.com/openears/
Based on Pocket Sphinx.
If you start here at wikipedia, you'll get a good list engines (http://en.wikipedia.org/wiki/Speech_recognition#Commercial_software.2Fmiddleware)
As I write this (June 24, 2009) it looks to me that are two viable open source solutions
Pocket Sphinx (http://www.speech.cs.cmu.edu/pocketsphinx)
Julius (http://en.wikipedia.org/wiki/Julius_(software))
Both have been used in iphone apps, but the iphone friendly source isn't readily available.
As I edit this (8 July, 2009) I recently learned that Loquendo (http://www.loquendo.com/en/) has voice recognition and speech synthesis (ASR & TTS) for the iphone.
The best approach will probably be to:
Record the voice on the phone
Send the recording to a server that runs the speech recognition software
Then return something to the phone to indicate what it should do
The Dragon Mobile SDK from Nuance does what is asked for. You need an internet connection to be able to send the audio to Nuance's server and you get a list of text responses. You can then decide what to do with the text responses (e.g. ask your user to choose the one he meant or perform some action). Here is the link:
http://dragonmobile.nuancemobiledeveloper.com/