We’re working hard to finish forScore 10.4, so today we’re taking a quick look at a useful but often misunderstood iOS feature: the Battery Usage screen. These usage statistics are found in iOS’ Settings app (in the Battery section) and they show all of the apps that have been used in the last 24 hours or 7 days.
Where people generally get confused is that the numbers shown here are percentages of the total power used, not percentages of your total battery’s capacity. If you start the day with a full battery and end with 80% remaining, then an app’s 50% reading means that it was responsible for half of the power consumed, or just 10% of your total battery’s capacity.
In other words, these percentages are highly relative. If you use an app a lot you can expect to see a higher percentage of usage. If an app’s usage seems higher than it should be for how much you use it, it may be operating in the background or could simply be managing resources poorly.
If you want to learn more about this panel, Apple’s knowledge base article offers a few additional details to help you understand how this information can be useful.
Today we’re happy to announce the release of our latest app, Badger: PDF Negotiator. Badger is a PDFKit-based property viewer and editor for the badly-behaved PDF files on your device or stored in the cloud. It integrates seamlessly with the Files app, supports in-place editing with many different apps (including the upcoming updates to forScore and forScore mini), and includes three action extensions so you can access its features from just about anywhere.
Badger is available now exclusively on the App Store at a special introductory price, so if you’ve got PDF files that need a stern talking to be sure to check it out and let us know what you think!
This week Apple announced a new iPad, the sixth generation of their most popular model and it sports some impressive specs. Most notably, it supports the Apple Pencil—the first iPad to feature this capability that doesn’t carry the “pro” label or price tag.
We think annotation is incredibly important and that the Apple Pencil provides the best experience hands-down, so we’re very happy to see this change. We want as many people as possible to use this amazing tool that really shows off some of the most intensive and creative work we’ve ever done with forScore.
Since we’re working hard right now to finish forScore 10.4, this week we thought we’d take the opportunity to share our previous Feature of the Week article on Apple Pencil in case you missed it. It’s a long one, and it touches on many of the changes we made with several updates between forScore 9.3 and 10.2, so it’s a great place to dive in.
It often feels like the potential for technology to solve problems is practically limitless. That optimism is incredibly important, but lately it’s also being tempered with an overdue reckoning over how that progress is paid for. From the fight over net neutrality to Facebook’s role in politics, people are starting to realize just how much of their activities are being manipulated and monetized on websites and within apps. So today we wanted to take a detour from strict features and discuss your privacy—a feature, in some respects, but one that’s defined by what we don’t do.
Plain and simple: we don’t collect any information from you when you use our apps. We don’t offer accounts or monitor your usage, anonymously or otherwise. Unless you contact us directly, we don’t even know who you are beyond basic anonymous sales reporting.
When we want to make sure your data is available to you on each of your devices, we rely on Apple’s fully encrypted services to do it and nothing ever comes back to us. If you use features like Cue, that information is shared locally between devices and nowhere else.
We trust our customers to tell us where we go next. It may be more difficult for us to work without broad insights into how our apps are used, but that’s a tradeoff we’re happy to make and our eight years of history prove that thoughtful development can come from relationships just as easily as it can from surveillance. In the end, we’d rather make a flawed app than exploit people to gain an edge on our competition.
If you want to read our complete privacy policy you can do so here. It’s short and easy to read so you can know exactly where things stand without hiring a lawyer.
There are millions of apps on the App Store and they share a lot of things in common, so Apple includes packages of shared code in iOS called Frameworks that let developers reuse features and components. Apple creates and maintains the code (making sure it’s secure and provides a consistent experience) so developers can adopt new features quickly and reliably.
PDFKit is the name of Apple’s framework for working with PDF files. It was introduced for the Mac all the way back in 2004, but it wasn’t until late last year with iOS 11 that they brought it to the iPhone and iPad. It helps apps display, search, and even edit PDF files in a variety of different ways. It reduces the amount of code we have to maintain and gives us instant access to functions we haven’t yet been able to write on our own.
It can also display pages and embedded annotations, which is something we’ve offered for some time now, but PDFKit was written by a much larger team and is constantly being updated and improved. Apple’s implementation is broader and produces results more like what you’d see in their other apps (on both iOS and macOS).
With forScore 10.3.5 we added the ability to use this new rendering code to display pages and thumbnails, but we disabled it by default until we knew for sure that there no unforeseen issues. We’ll be enabling it for all users with a future update, but you can see the difference for yourself by turning it on in forScore’s settings panel. It only affects the way pages are displayed within forScore, so if you don’t like it you can always turn it off again without any negative side effects.
If you don’t see any issues, leave it on! Apple’s engineers have put a lot of work into making PDFKit, and they know a lot more about how iOS is built than we possibly can.