我们正在尝试为客户端构建一个照片应用程序,其中需要使用web服务来获取大型照片。这些照片将是大小不等的高分辨率JPG(大约在5-7MB之间)。
我们面临的问题是如何获取一批照片(比方说10-15张),将它们存储在应用程序本地,并允许用户对它们执行编辑任务。我从我的团队中了解到的是,如果我们编辑高分辨率的照片,它将由于内存而使应用程序崩溃。这意味着我们将不得不降低照片的分辨率和大小,这是合理的,但可能需要一段时间。为了保持良好的用户体验,下载和减少照片的最佳实践是什么?
为了提供一些背景知识,我们正在为Android和IOS构建这个应用程序。预期的功能是典型的滑动,收缩,使用基本编辑和高级编辑的编辑,如框架,文本覆盖等。
发布于 2015-02-02 06:14:39
我不确定这是一个关于应用程序架构的UX问题。也许更适合于StackOverflow或其他堆栈交换站点,但我将尝试从UX的角度来处理它……
用户期望
- If they expect to have control, you could check disc space or device capability before downloading & offer them a choice of smaller size vs. slower response time. - For example, if they're on an older non-retina/low-pixel-density device, display an alert that editing high-res images might be difficult & offer a smaller version as an alternative.
- How will saving/uploading edited versions work? Users might be upset if they overwrite originals w/lower quality versions & weren't given an option to "save as" or set quality level.
使用情形和设备规格
- No mobile device is large enough to show multiple high-res images on screen at once anyway. Keep current image in memory; only show thumbnails of others (saved on disc) until requested for editing & then swap; release/reload resources as necessary.
- Are you saying this is not the case?? Can't even open 1 image? Is it being saved to disc first, or opened in-app directly from web service?
保存每个图像时验证存储空间是否充足
- If device storage is full, cancel remaining downloads & alert user which images are missing
可用性和响应性
- Download individually & save to shared location. This keeps them organized as a batch of 10-15, but lets the user start working as soon a the 1st image is available. Don't make them wait for all of them.
- Could use a separate "downloads" view w/progress bars & let user continue work in another tab/view
https://stackoverflow.com/questions/28277121
复制相似问题