- 02-17-13, 03:32 PM #51
say you're in an app. pinch from opposite corners (or some other unused gesture) and it instantly kills the app. No minimising first.
if it can be done anywhere then that should save the need to go to the main menu to get to the button as well, and can save another step.
i use the pinch gesture as its highly unlikely you would do that by accident and prevents on accidentally killing apps.
may be too much, but i can see the benefits of a kill button
- 02-17-13, 03:39 PM #55
Well if they could find a suitable gesture, i'd prefer that. if not the button could work fine too.
I suppose Blackberry would have to implement the gesture though and that would not be a priority, whereas the dev can choose to put the button on the app they make tomorrow if they so wish
- 02-17-13, 04:14 PM #56
- 02-18-13, 07:19 AM #59
- 02-18-13, 07:20 AM #60
On the PlayBook, as I recall, we don't have to use the X to kill an app. Once it's in Active Frame status, swiping the frame again up toward the top bezel kills it. I don't have the PB with me or I'd test it now. Does this work in BB10?
- 02-18-13, 03:57 PM #67
- 02-18-13, 05:57 PM #69
But I do get the concept of letting the OS do the housekeeping. Maybe the concept of "active" frames is misleading. In some cases, the frame may be active in the sense of actually doing something while "minimized" (activized?) but it many cases apps are inert when the user isn't doing something with them. Inert apps don't chew up the battery. Let the OS dump them when it needs the RAM.
- CrackBerry Newbie
02-18-13, 10:54 PM #71
- 7 Posts
I am going to jump on the disagree train here.
Although the idea may sound appealing, you may be over-thinking where that close button is found: on the "landing page". Typically the landing page will be the root of the application, and doesn't have much navigational clutter. Thus Photo X has plenty of room for their "close" button.
The second you open an application and perform one tap, you will likely no longer be on the landing page. Once this happens, you typically have more content on the screen, and perhaps an action bar on the bottom with a back button. Having the close button here will be more cluttered that the Photo X landing page example.
In order for me to consider the button being useful, it would have to be always available. If it wasn't then this means it would only sometimes be available, which is confusing and inconsistent. So in order to maintain consistency, you would always have a "close" button on your action bar (or somewhere else taking up room). This is wasted real estate, and wasted development effort.
The other downside is that it is not enforced in any way. Even if Blackberry asks all developers to add this button to their apps, it is not programatically enforced (unlike the swipe-up gesture), and devs can simply decide not to do it. All you will end up with is an uncertainty of when this button will be available. This is very unpleasant because you never know what to expect. On the contrary, Blackberry has actually suggested that you shouldn't include a close button. Devs can include it, however users can always rely on that close gesture being available. Developers need not spend 1 minute implementing/designing/testing a close button, it is already done.
I could go on and on about this, there are many, many different reasons why developers shouldn't be adding custom close buttons.
- 02-18-13, 11:12 PM #72
Word to developers, please implement an Off buton
As a developer, I have little choice but to respect the guidelines. The choice must be made by bbry and backed by their sdk team. Otherwise your asking for trouble (another excuse for appworld team to reject an app, breaks in updates, issues on platform enhancements, everypne creating buttons their own way, etc etc).
Cool idea but rules are rules
Sent from my BlackBerry S10.1 using Tapatalk Touch Beta
- 02-20-13, 10:05 AM #73
Word to developers, please implement an Off buton
- 02-20-13, 10:30 AM #75
In software development you have an existing platform under which you have to develop. Developers have to maintain the design integrity for the platform for which you are developing. You cannot violate that integrity.
Within the business model of software development, BlackBerry is the business owner. The developers are contractors to the business owners, they design to the specifics of the business owner. The customers of BlackBerry are the carriers, they sell phones to the carriers who then sell to their customers. The customers of the carriers are the end users.
You are talking about end user satisfaction when you talk about customer satisfaction. The end user does not direct software development, they would send requirements to the business owner who then puts then in a backlog for development. Feedback from end users should be used by the business owner to determine which backlogged items should be put in development. However, the end user does not direct development directly to the developer or contractor.
- By sitegia in forum BlackBerry OS GamesReplies: 0Last Post: 08-26-09, 06:41 PM
- By rob88 in forum BlackBerry OS AppsReplies: 7Last Post: 05-02-09, 03:23 PM
- By Snazy in forum Rehab & Off-Topic LoungeReplies: 0Last Post: 04-20-09, 05:18 AM
- By jhamilton3 in forum Apple iPhone/iPadReplies: 5Last Post: 02-11-09, 12:21 PM
- By martymann in forum BlackBerry StormReplies: 1Last Post: 11-26-08, 01:55 PM