Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iPad Quasar iOS 6.1
- Thread starter derrick2005
- Start date
- Sort by reaction score
How many Android tweaks have you updated when they've been abandoned by the author?
At least it's much-much easier to write tweaks for Android than for iOS, the system being much more open. And, incidentally, Android 4.x's API itself is much-much more powerful than that of iOS. (I program for both Android and iOS so I know what I'm talking about.)
Developing JB tweaks for iOS is a gamble. Something that works today may not be possible to implement tomorrow at all, under a newer version of the OS. The case seems to be the same with Quasar.
While this is all true, Mrg02d's simplistic statement is irrelevant, since it implies that, even if an Android programmer abandons their tweak, having the open source some how benefits the 'tweak community' at large.
It only benefits the community if another programmer takes over the code. An obvious conclusion, but needed when people wave the 'Android is better because it is open source' magic wand.
No app or tweak, even commercial ones, are guaranteed to be forever. The nice thing about both iOS and, I assume Android, it is up to the end user. People who did not upgrade to iOS 6, can still run Quasar. It was their choice to upgrade and to complain about the consequences is juvenile.
Last edited:
I wouldn't recommend using that argument in public, seeing as how many features Google has disabled in Android in the last few versions.
There are a lot more Android community hackers / coders capable of developing tweaks simply because:
- (when it comes to the kernel) it's far-far easier to find out what's happening. After all, you have the source code of the OS. What about iOS? You have far less resources. No easy-to-search API's (not even ones published by JB devs), no discussions, no nothing - as opposed to what's available on Android (or, for that matter, "legal" iOS programming, which is also very well documented by both Apple and practicing devs at, say, StackOverflow.)
Like my case: I'm a seasoned iOS developer and have also written some JB apps / tweaks (see e.g. https://forums.macrumors.com/threads/1538193/ ). However, I don't think I'd have the nerves / time to find out how a Quasar-alike app should (could) be written. For my tweaks, I've searched high and low for well-written, complete resources from other JB devs. NOTHING.
- it's way easier to test your apps without being in fear of losing the JB of your iDevice. JB devs may continuously be frightened by their losing JB if they do something wrong. This can also be a reason for the slow pace of Quasar for iOS6 development - the dev is just afraid of losing his JB by having to restore after a fatal mess-up. And he, of course, can't test iOS6 compliance on iOS5.1.1 (for example, an easy-to-JB iPad 1.) or Quasar compliance on still-6.1.3 JB'able/restorable iOS6 devices (e.g., the 3GS) because they don't include any iPad models.
----------
[/COLOR]
You mean forcing programmers not to use something in the Android API (not the Maps API)? I haven't run into any of these. On the contrary: Google's development model is far more old model-friendly. For example, in iOS, after Sept/2012, you can no longer use development targets less than 4.3, which means all 1st/2nd-gen devices are impossible to develop for in recent Xcode versions. In Android, you can write an app that runs equally well on an OS 4.2 (latest) than on an OS 1.6 (first) device, using even the latest 4.2 API's on the former devices. (I've elaborated on this question more thoroughly at https://forums.macrumors.com/showthread.php?p=16894740 , BTW.)
I think the opposite of what you stated is true. The 4.x Android has tons of new API's for, say, a lot of environment sensors. (Does the iPhone has a temperature etc. sensor? Yes, a rhetorical question.) The API support of background task management is phenomenal - just compare it to that of iOS. (Not possible on even JB'n devices - see the threads here asking for an iOS5+ equivalent of the venerable pre-iOS5 "Backgrounder" app.) And the list goes on....
API-wise, iOS has pretty much stalled in the last 1-2 years. As opposed to Android, which has become a real heaven for programmers wanting power.
Last edited:
Are we ever gonna see a working Quasar for 6.x? An iOS 7 announcement is around the corner. I'm feeling robbed for paying for this tweak and it's not being supported. I know the kid who made it says there is 1 thing he can't figure out for it to work properly, but what is he gonna do for iOS 7. Surely that will be more complicated to write code for and up till this point if he doesnt even have 6 figured out, what about 7? I felt I wasted my money, this is one of the few tweaks I paid for and is turning me off to support future developers.
I'm absolutely sure he wouldn't have quoted $10 for Quasar, had he known he couldn't update it for iOS6 compatibility.
Unfortunately, JB development will always be like this - a gambling game / black box development for us devs. There are a lot of things that simply can't be done under iOS6; for example, even hiding the status bar (see “SB Hidden Statusbar” and Flex's dedicated hacks - they worked just fine under iOS5 but in no way under iOS6).
Heck, even non-JB dvelopment does suffer from the same from time to time. For example, in iPhone 4S'es, Apple has made it impossible to record at 720p60, which was possible in pre-iOS6 times. Some AppStore apps suffered from this iOS dumbing-down; for example, FiLMiC Pro. Its successor, FiLMiC Pro 2 was even removed from the AppStore because it no longer could record at 720p60 under iOS6.
It has always been possible (even in 2.x times - see http://stackoverflow.com/questions/4264072/how-to-hide-status-bar-in-iphone-application ) to hide the status bar from your app. However, you can only control the statusbar while in your own app - to provide a system-level one, you need to hack into the system. This is what doesn't seem to work now under iOS6.
Ah, I get it now. Thanks for that clarification.
Sorry, MR Forum Police Officer. Will I receive a citation this time or can you let me off with a warning this time?
My experience is people who think rules don't apply to them do not respond to warnings or citations.
Clearly you understood that I was addressing a bit of information in Menneisyys2's post about JB development and the constraints in iOS 6 that has seen Quasar's development either stagnated or halted, using this as a moment to learn something about an API in app development that I didn't know before, right? As I mentioned, it was off-subject, but still related to the veil of app development from the SDK and for Cydia, as introduced in Meneisyys2'sand my subsequent posts. There wasn't a grand deviation at all from the thread subject at all.
Ignore him. All I see from him are these style posts. He's unhappy...I know him in real life. An unhappy mac user.
No, you do not know me which makes you a liar.
----------
Save your sympathy for the liar. And everyone always has a good reason for not following the rules. It's called rationalization.
/end
Probably only the fact that Quasar will be needed in the iOS7 times too - Apple, it seems, won't add windowed / split-screen multitasking in iOS7. (See https://forums.macrumors.com/threads/1597464/ )