Build Verification Testing (BVT), also known as Smoke Tests or Build Acceptance Testing (BAT), is a type of software testing that is aimed at ensuring the most important functions work correctly when you push new code. The results of this testing are used to decide if a build is stable enough to proceed with further testing. Typically the BVT process is automated.
Hybrid can mean multiple things to many people in the mobile development community. Typically a hybrid app means it’s using Xcode + Swift, and conforming to all the platforms conventions regarding navigation/presentation. The building blocks of the app are composed of UINavigationController, UITabViewController, UISplitViewController, UIViewController, etc. Within those containers, we can have many screens where the content is built using UITableView or UICollectionView, we can have even more where that role is filled by a WKWebView.
Ever wondered what it would take to create an app faster with less code?
It should have a reliable or at least stable code with good device and network performance. The code should be easy to understand by anyone and easy to upgrade/add new feature. I know, this is not as easy as writing a quick paragraph.
Welcome to my world!
I have been developing mobile apps for the past 7 years and I have tried every option that’s out there to achieve above five points. Currently, I have settled down on few of these tools/principles.
Code signing your app assures users that it is from a known source and the app hasn’t been modified since it was last signed. Before your app can integrate app services, be installed on a device, or be submitted to the App Store, it must be signed with a certificate issued by Apple. At TestGrid we use real devices, so we must use the signed version.
When creating an app, developers must undergo the many twists and turns that come with the development process. From planning to testing, the entire experience can seem a little like playing a board game with checkpoints and objectives. In this blog post, we’re going to discuss the advantageous course of the Software Development Life Cycle (SDLC).
The first phase of the SDLC relies on the identification of risks and problems within the current market before the blueprints can be broken out. While you may be eager to start right away, it’s important to know what to avoid before you begin. Think of it as laying out the entire game board and looking over it to strategize before you play. What’s your approach?
Just as Jason Derulo famously sang in his popular song Talk Dirty to Me, it is possible to make your way around the real world without properly learning all of the languages. In the world of mobile app development, there is no way around learning a language or two. We’ve been around the world and (unlike Derulo) we speak the language.
This edition focuses on the programming language Java.
This week’s blog post is a feature on Android Integrated Development Environments (IDEs). Since in our previous post we discussed the IDE associated with Apple, we thought it was only fair to discuss Apple’s competitor, Android. Unlike Apple, which has one main IDE, Android has two front-runners and a couple less popular choices. The two leading competitors are Android Studio and IntelliJ IDEA, which are both powered by IntelliJ.
Programming languages are used to give technological devices, like computers or smartphones, commands they can understand. Just like there are many different languages spoken all over the world, there are many different programming languages. Each language has both a unique syntax (terms that it understands) and a specific set of rules for ordering program instructions. Programming languages are commonly used by programmers to develop software programs, scripts, or other sets of instructions for computers to execute. In today’s post, we will be covering two languages, Swift and Objective-C, as well as an Integrated Development Environment (IDE) they can be used with called Xcode.
