The user experience is golden. Without the user, a mobile app cannot succeed. This is why it is important to ensure bugs do not drive users away.

Bugs ruin the user experience and damage the developer’s brand. Users with low patience and high standards are quick to leave nasty reviews and uninstall. Additionally, in an effort to protect their users, the App Store and Google Play Store will reduce an app’s rankings if it has too many performance issues. Ultimately, bugs can sabotage an app’s success. Thankfully, with Bugsee, developers can protect their user experience and increase their chances of succeeding.

If you’re new to app development in Android, file upload might appear like an uphill task. But in reality it’s just two things — requesting permission to access the sdcard/camera, and then making API to upload the files. Unless your requirements explicitly ask you to manipulate the files or optimize them in some way, things are fairly straight forward. In this post, we’ll talk about some of the common challenges and some of the best practices to rectify those challenges while creating a file uploader in Android.

You probably wonder whether you need Bugsee and is it any good? Well, let me try to address these here.

VIDEO

Have you ever wondered how your users get to a certain state in your app? Have you ever tried to recreate an intermittent bug? As developers, we deal with these types of issues on a regular basis. That’s where Bugsee can help.

Holiday season is upon us and I wanted to wish that your mobile app will be super stable and bug free in 2018, which in turn, will result in a healthy user growth!

Recently I took a close look at our support tickets and it became obvious that some of our existing features aren’t easily discoverable. While we’re looking into it, I wanted to highlight a few things of what Bugsee can do (well, on top of video recording of live apps).

Remember how we said your Swift or Objective-C code is compiled into ARM pr x86 machine code? Well, that is not entirely true. Before producing actual machine code, compiler first creates an intermediate representation of the code called bitcode. It is not your code, bot not yet a machine code either.

In this article we will see how to manage builds for Swift projects, examplified with PackStream, through Jenkins, an open source build server. We will build it for iOS, macOS, Linux, watchOS and tvOS, and make sure it builds both through the Swift Package Manager, Cocoapods and Carthage.

This tutorial is a revised tutorial we’ve published earlier, called iOS Ad-Hoc distribution using Amazon S3. The original tutorial achieved the desired effect using s3cmd and a bunch of bash scripts. However, since its publication, Fastlane gained a lot of popularity and gathered quite a following around it, including the ecosystem of plugins. If you are not familair with Fastlane, you should definitely spend some time to get familiar with it, and see how it can help you automate your iOS and Android builds. In the following article we will only focus on one specific task – creating an Ad-Hoc distribution on Amazon S3, and will use one Fastlane plugin for that purpose, called aws_s3.

We have already covered why certificate pinning in mobile apps is important and have shown how to implement it both in iOS and Android. For the sake of simplicity, we had to omit a lot of nasty details and corner cases from our example. In the real world, the code might get complex with time very quickly, when you have to support various legacy iOS platforms, various popular networking libraries out there etc. Luckily, nice folks at DataTheorem have created and open-sourced a framework for SSL pinning which eliminates that simplifies most of it.

In this day and age more and more user data is stored electronically. Users are expecting end-to-end security from every application they are installing on their devices. Application developers too, are seeking to secure all communications between their apps and backends in order to prevents hackers from reverse engineering their protocols and getting access to their databases.

The most basic form of security when transferring data between the application and the service backend is SSL/TLS encryption, and it is very common for developers today to switch their traffic to https and declare their communications as secure. In fact mobile platforms today make it really hard for developers not to use https. That by itself, however, is not enough. Encryption is useless when communicating parties can not validate the identity of their piers.