Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
Simple question - How do Snapchat stories load so fast, and even when I "skip" an item, the next one is always ready?
Snapchat stories is a mix of images and videos, whenever the screen is tapped, the next item starts instantly, no matter if it's an image, or a video. I have never seen any delay in the app, and I'm wondering
How do they do it? Do they cache all the content once the app is started (highly unlikely)? Do they continuously pre-load upcoming items while you are watching a story? Do they load everything when I tap the story? I do not understand the "magic" behind the flawless stream of content. Also: What does the backend provide? A list of resources?
Does anyone know how they do it? Other apps like Yeti or Fleek pretty much do the same thing, executed in the same flawless manner. I'm a somewhat decent iOS developer, yet I have no idea of the method that is used here.
The use case allows for background-readying on the app side, and caching on the back end.
So how I'd do it is something like this:
When the app comes into focus, have a background thread find some links to the stories that come right after. Also if you get toward the end of the cached content, look ahead some more. Possibly have some sort of visual animation so people can't flick to the very end without giving the app a chance to load some data.
Since you know what comes after, the back end can move all the content to cache, where it will feel nice and snappy. The fact that SnapChat is not supposed to be persistent helps a lot, because once the recipients have seen the stuff you can remove it from cache. Also since recipients are not editing the information, you don't have a cache coherence issue (actually can you edit stuff? Haven't looked in a while).
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 6 years ago.
Improve this question
I have an application which was rejected. The rejection says it contains lower quality experience, and I should add iOS features to it, like a favourite button.
It's a language learner application, which is just a "webview", so it does not contains much, but textviews and a few pictures. Though it has a nice design and a lot of animation, but still don't have that interactive thing or button.
Could anyone help me by showing me the way how to improve my app to be accepted?
How can I make those iOS features?
What buttons should I make and how?
I know there is a lot of way to do these, but I'm asking because I'm not a programmer and I believe you can explain it to me, or link me the right pages to learn and achieve my goal.
Appreciate any help.
On Android it was fine to just make that "lame" application which has nothing but textviews with pictures.
I also don't want my users to have internet connection while using the app.
Basically, I just need buttons which can do something.
I'm guessing you didn't read the app store review guidelines
The second point in the introduction reads…
If your app looks like it was cobbled together in a few days, or
you're trying to get your first practice app into the store to impress
your friends, please brace yourself for rejection. We have lots of
serious developers who don't want their quality apps to be surrounded
by amateur hour.
Please don't waste the reviewers' time with a "language learner application" - write and submit something of value
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I'm trying to figure out if it is a requirement for apps submitted to the iOS appstore to show the progression of data being down/loaded (by means of a progress bar or something similar) or if simply letting the user know that loading is in progress is sufficient. My app generally only loads for 2 seconds so i figure showing a progress bar is not really necessary but if it is a requirement then obviously i have no choice. Here's hoping someone can enlighten me :)
For a two second load (and you can ensure that that's pretty much what it will ever be on all devices supported) I think you should be perfectly fine. Think of Apple reviewers as the most impatient user you have ever encountered. If you normal user is watching you app load and thinking "Is it frozen or still loading something?" the Apple reviewer is going to say it's frozen and close your app and start the write-up saying it froze.
For short activities I see no need for a progress view (I do them anyway, but that's just my preference). For long activities make sure to show some progress indication other than the beachball of death activity indicator.
I think it's a mistake to assume that Apple has "requirements" for UI elements. The UI Guidelines are just that - recommendations on how your app should behave when there's no better reason to behave otherwise. Every app writer should develop a user interface which works best for his app and his users. If you don't have a reason to break the guidelines, then follow the guidelines. If you do have a reason, and it's worth it to the user to do it your way instead of the Apple way, then do it your way.
For this particular purpose, though, I like the progress view. The reasoning being: suppose the load fails. A progress bar with no movement indicates failure, but a message saying "loading..." that continues to sit will make the user feel the app is still gainfully employed.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions concerning problems with code you've written must describe the specific problem — and include valid code to reproduce it — in the question itself. See SSCCE.org for guidance.
Closed 9 years ago.
Improve this question
After some searching, I've discovered that there's nothing I can do from my app to open one of the major map apps and start turn by turn navigation immediately. (If you know, please tell me)
In Google Maps, Apple Maps, and Waze, I can deep link into the app and have the route shown to me (usually by setting "saddr" and "daddr"), but human intervention is still required to actually start the navigation. All of these are one click away, but then the actually "Route, start, or go" button is quite small and hard to hit on a phone while you're actually in a car with your phone on a dock.
I'm just curious why this is, I can't figure it out. The only hunch I have is that they have to open a more persistent connection with the device and they want to avoid DoS attacks or something like that. It seems like an easy flag to put in their API, and I've seen various other questions trying to do what I'm trying to do.
And even if all that is true, they can still probably have a different flag where navigation is one click away with a button that covers half the screen, much better than a button barely the size of my fingertip.
Hopefully someone has some expertise on this so I don't go yelling at engineers working on the map apps.
The answer is simply that none of the major map app developers have allowed this. There is no technical reason why iOS apps couldn't do this; they just don't. The decision is probably because they want to require user interaction before starting directions, as most apps allow the user to edit parameters or choose one of several routes before navigation starts.
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 9 years ago.
Improve this question
Our app involves the use of techniques that have not been used within the target profession before, and as a result, end users will have no comprehension of how to use it. We will be doing webinars to help them get started with it; however, there is a concern that they may need some immediate assistance from the time they download it.
So, we're trying to figure out how best to present this information. While the app itself is mostly self-explanatory, the underlying techniques on how it is to be used require some explanation.
I'm thinking of adding a "help button" on the nav bar at the top of screens where it will be relevant, which would then open a webview to load html containing the necessary help screens.
My questions are:
a) Would this generally be acceptable in terms of the UI?
b) Is there a better way than what I'm suggesting?
TIA
A: No. I think a help button is the wrong way to go about it.
B: Why not display a screen onto of the UI that gives info on how to use the app. This screen only shows the first time the user opens the app. Like a short tutorial?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
We have different forms of documentation for our desktop apps, but until now most iOS apps have been fairly self-explanatory so we've been able to get by with simple hint strings in settings etc.
But for a more complex app I'd like to be able to create a few HTML pages that look approximately like native iOS UI and are easy to maintain.
Dashcode has a browser template that seems to fit the bill, but it's terribly buggy under Lion. I could start from scratch using something like iUI, but I'm wondering if there isn't something readymade already out there that would fit the bill?
Requirements:
- One or possibly two levels of hierarchy
- Display short formatted text with images
- Preferably HTML so the documentation authors can create and format the content on their own without touching the dev side of things
Any ideas or tips would be appreciated!
I use CSS formatted HTML pages that can either be included in the project or served from the web or actually both (you can do a check so see if the app has a connection to the server and if so serve them up from there or serve them from a local resource).
I personally think the Static Cell UITableView is the ultimate way to display those help options. That and Storyboard were the two big favorites for me in iOS5.