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 8 years ago.
Improve this question
Apple's announcement of the 'Optimized for iOS7' mandate is as follows:
https://developer.apple.com/news/index.php?id=12172013a
Starting February 1, new apps and app updates submitted to the App Store must be built with the latest version of Xcode 5 and must be optimized for iOS 7. Learn more about preparing your apps by reviewing the iOS Human Interface Guidelines.
There's been several questions regarding this already regarding the Xcode part, which seems fairly straight-forward (use Xcode 5!)
But the 'optimized for' part along with the HIGs is much more vague.
It appears that some interpret this to mean "It has to look like a native iOS7 app...Helvetica Thin, extremely flat icons, translucency, etc"
But I find that hard to accept given how broad app UIs tend to be. I don't see EA Sports changing all their UIs to match, for example. Has apple published any clarifying documentation in regards to what they mean by 'optimized for' and how closely the UI must adhere to iOS7 conventions and to what range of apps this would apply to (all apps? Only native apps? HTML5 apps? Games? etc.)?
Coming from someone who has submitted a lot of apps, this isn't something I would see Apple enforcing unless you stray very far from the iOS 7 look and feel.
For example, I could imagine someone trying to submit an application that looks & feels a lot like an iOS 6 app, which is something they wouldn't want (confusing). Or, imagine somebody creating a new UIDatePicker that looks like the iOS 6 date picker (confusing). They're simply looking for consistency.
So, rule of thumb when it comes to HIG--use what apple provides. For custom views, respect the platform and don't confuse the user.
More specifics https://developer.apple.com/appstore/resources/approval/guidelines.html
One current completely unsupported working hypothesis seems to be that, as of Feb 1st, an iOS app has to be built with the iOS 7 as Base SDK, and that the newer iOS 7 metrics can't break anything in the UI (as in non-operable buttons or alerts, views partially-hidden under the status bar or behind tool bars, text half off-screen, etc.), and the app can't attempt to call any deprecated APIs removed from iOS 7.
Related
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 7 years ago.
Improve this question
My company has an app built using FileMaker Pro, and it is not a great app. It's not user friendly and it is hard to use. It also doesn't do everything that we need it to do. I don't know anything about Filemaker Pro, but it seems like it's an older system. Most people building iPhone apps are coding in objective C and swift right?
Does anyone have any input on Filemaker Pro? Anything you share would help. Is it old? Does it have a lot of limitations? Is it popular to use when building apps? Does anyone still use it or are most apps built in Objective C and Swift with a text editor?
Thanks for the input!
Your question is really off-topic for StackOverflow, but I will provide a couple of pointers:
FileMaker is not old - it's very current.
FileMaker is not a tool for building iOS apps. FileMaker is a tool (or set of tools) for developing and deploying cross-platform database solutions. One of these tools is FileMaker Go - an iOS app that will run a solution developed in FileMaker. This appears to the user as a native iOS app.
If the solution does not fit your needs, the fault is more likely to lie with the developer than with the platform.
If you're not running FileMaker as part of your business, then FileMaker Go is probably not the best choice for you.
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 7 years ago.
Improve this question
I am learning React Native and considering developing IOS apps for my clients in it. I'd like to see some sample apps in AppStore, but there is just one. Why is that?
I see so much hype about this technology, but it looks like almost nobody uses it. Or is there any other reason for it? I'm already working with React and would like to add React Native to my skills, but don't know, if it's worth it. There are some interesting tutorials on the web, but no real samples in AppStore.
Actually there is already an app in the app store according to this blog post.
And as far as I know two of facebook's apps have been built using react-native (maybe not completely ): Groups and Paper.
So if you have any concerns, whether react-native is production ready: I think if Facebook can use it in their production apps it's probably good enough for you too ... ( no offense ) :D
People are still bootstrapping their knowledge and building applications.
Also, the technology is still in its infancy.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I am developing an app for windows phone 8.1 . Based on MSDN design guidelines I am using pivots and panorama controls in my application.
I heard there are some significant changes in UI in windows 10 OS and MSFT is not using popular controls like pivot and panorama in Windows 10.
MSFT uses buttons ,top bar, hamburger menu etc. mostly in their new OS version. See the link
My questions is , can we design my new application in 'windows 10' model ? (using hamburger,top bar etc.) . I want to make sure they will put my app in store. I am afraid of certification failure (there is a chance for rejection because app may not follow WP 8.1 app design guidelines)
This is actually a big app and need at least 8 months to get done .
Those design guidelines are not certification requirements, they're just here to help you get a clue of WP design principles. There are some UI requirements for publication, but those are more semantic (i.e. text on buttons should always be clearly legible). The official requirements are stated here. As long as the UI is responsive an not misleading for users, you won't have any problems.
Personally, I've published several apps to WP, including some with special, non-standard UIs, and got rejected quite a few times, but never because of disregarding design guidelines. Mostly, it was due to technical reasons, or the button example I stated above.
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 8 years ago.
Improve this question
I'm developing an app using Titanium Appcelerator.
It's a simple flashcards app for iOS which allows users to scroll through a selection of foreign words, and view the equivalent english translation on 'the other side' of the card (flip transition!). Each card has an audio link and there are a few options for the user to choose also.
I would like to know if anyone reccommends the use of the alloy framework?
Does it speed up the development time?
Are there any use cases where alloy would not be appropriate?
I think your app is definitely appropriate for alloy, the same things appropriate for Titanium in general work with Alloy. One of the key things to think about is that using Alloy will not necessarily speed up development time. That is not the goal, the goal is to separate the concerns (Model View Controller), and provide cross-platform and multiple form factor support. If you are interested purely in speed of development stick with regular Titanium.
However, where it can speed up dev time is in your persistence strategy, sql integration of models is built in with Alloy. So, if this flashcard app your thinking of creating has the users creating flashcards on their phone, then using them later, I would definitely go with Alloy to take advantage of the model stuff.
Take note that the documentation is kind of sparse, I ported an existing clients project to Alloy and really had to find my own way on a lot of things, but It was not a simple app.
Essentially, if you want to 1) Release to multiple platforms and form factors and not have migraines, 2) Have a built-in easy to use persistence strategy, 3) Be able to maintain your code at a later date, or have other people look at it and be able to tell whats going on, then I would definitely use Alloy.
Here are some links that will help you to know more about alloy framework,
1 Official appcelerator doc
2 A presentation on Alloy framework
3 Google group : Appc Ti Alloy
4 appcelerator / alloy in github
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I want to code some applications to use touch screen gestures. What is the latest technology available?
What functionalities to APIs provide? Is it just the casual select and click functionality or are advanced gestures are also exposed through the API? Is it possible to extend the APIs to code my own gestures?
I can't arrange a touch screen device immediately. Is it possible to do some coding now and test my code using an on screen emulator with my mouse? Later for thorough testing I will get an actual touch screen device.
I am open to Linux and Windows platforms.
Also would like to explore both desktop (PC and laptops) and mobile platforms (smartphones) with greater stress on the former. Desktop because the computing power available is high and don't want to be bogged down with mobile related issues in the beginning.
Windows 7 Mulit-Touch has APIs for both touch and gestures. Gestures are extensible. (See http://msdn.microsoft.com/en-us/library/dd371406(v=VS.85).aspx).
The Surface Toolkit for Windows Touch Beta (http://www.microsoft.com/downloads/details.aspx?familyid=801907A7-B2DD-4E63-9FF3-8A2E63932A74&displaylang=en) gives you additional, multitouch enabled controls that were introduced with Microsoft Surface.
Finally, the CodePlex project "Multitouch Vista" allows you to simulate multitouch on a normal computer using 2 mice (http://multitouchvista.codeplex.com/). It takes a little fiddling to get to work, but it does work nicely under Winodws 7, 32bit and 64bit.
Hope this helps!