February 2, 2016
Category: App Development
Last month we talked about how important it is to conduct market research prior to embarking on an app development project. It’s critical for success to begin with a clear definition of your value proposition and target customer, as the technical requirements for your app should be informed by market needs/desires.
Once those are understood, one of first technical choices you’ll make pertains to which mobile operating system to use. Will your app be available for Android users, iOS users, or both? Your research may make it clear that your target audience has a strong preference for one device type or the other. If not, you can consider other factors like OS market share or OS upgrade adoption rates.
This is an important decision because the answer influences the development tools used to create your app. iOS and Android apps are written using different programming languages, so an app by default will only run on one platform or the other. In many instances, it makes sense to develop for both platforms. When that’s the case, the discussion often turns to the topic of native vs cross-platform development. We firmly believe this is a topic worth discussing with your app development partner, but we’ll share our experience with you so you have a starting point for consideration.
August 16, 2013
Category: App Development
For this week’s Lunch and Learn, software engineer Will Helling gave us an overview of the changes he’s discovered as he works to make our ePCR for iPad app compatible with iOS6 and the forthcoming iOS7.
Here are some of the highlights of his presentation:
Design – while the presentation was largely about changes from a developer’s perspective, it’s impossible to talk about iOS7 without mentioning Apple’s radical design changes.
Although they’ve kept their main color scheme (white, blue, grey and black,) Apple decided to allow whitespace to dominate the new design. We noticed that this helps make the content “pop,” compared to the overwhelming frames created by the various toolbars in iOS6.
View control overrides
In iOS7, view controls are automatically set to fullscreen, covering the status bar. However, iOS6 does not have this feature, leaving an awkward gap between the status bar and the view. To ensure compatibility with both operating systems, Will had to use a command that would force fullscreen in iOS6:
iOS7 requires developers using Flurry to update to the most recent version, 4.2.3 – apps not using this version may experience “irrevocable data integrity issues.” Since providing the best tools based on our users demands is a core function of ePCR for iPad, updating this feature was absolutely necessary. In order to update, Will had to download the new SDK and make sure to include Apple’s security framework and ad support framework. And… voila! Flurry is compatible with iOS7.
Will also ran into some backend issues with libraries. iOS7 links to the new XML library… but the old XSLT library is incompatible with the new XML library, and the new XSLT library is incompatible with the old XML library. This required Will to do a manual universal compile of LibXML.
iOS7 will be available to consumers sometime next month, but with some users slow to adopt to a new OS, we’ve emphasized making sure ePCR for iPad works on both systems. As these new changes roll out, we also plan to introduce some new features, like a “night mode” that will be easier on users’ eyes at night.
We have a weekly Lunch and Learn where team members share different aspects of their work. Have a topic you’d like to know more about? Let us know in the comments!
Interested in industry news and trends?
Sign up for our monthly email to get the highlights on technologies and innovations impacting mobile strategy.