The core value of this group is to bring developers up to speed with BB technology, concentrating on BB10.Exploring efficiency, beauty and power BlackBerry provides to its users by designing Apps that can be used globally and that improves developers life as it improves community life.
Like last week, we would like to focus on one of those apps and ask the developer some insights on how the app was developed, where the idea came from and so on.
This week, the app we would like to feature is “Work Wide” developed by one of our Developer Elites, Brian Scheirer (@brianscheirer), together with another dev, Olaf Hanson (@olaf_d), both based in US.
“ Work Wide is specifically designed to allow for maximum productivity on your BlackBerry Passport. Using the wide screen, Work Wide lets you have two “apps” side by side.
It has a built in Web Browser, Composer, Calculator, Picture Viewer, and Txt Viewer.”
We asked Brian a few questions.
Where does the idea come from?
Originally Work Wide was exclusive to the Passport because while watching the launch event it dawned on me that I could provide a really unique experience to Passport owners with an app that utilizes its unique form factor. The idea to expand support to other devices was purely due to popular demand.
How long did it take to develop the app?
The version that is released today is the result of 2 developers (myself and Olaf Hanson) working continuously since Oct 2014. The beauty of this type of app is we can indefinitely add more integration and features as long as there is user interest.
What are your ideal customers?
Work Wide’s target audience is much the same as BlackBerry as a whole target audience. We want to help people who want to “get things done”. And with Work Wide we hope to create a natural extension to the BlackBerry experience with different take on the multitasking workflow.
Why should our customers buy your app?
First off there is nothing else like Work Wide in BlackBerry World. Second as I said above, we are catering to what BlackBerry users want: multitasking, efficiency, and productivity. And more to that point, Work Wide hopes to push the limits of what it means to do things like multitasking with a wide variety of use cases.
“Work Wide is developed by two passionate BlackBerry developers who have also been BlackBerry device users (by choice) for many years. We are both very excited about what we’ve created so far and plan to continue our development efforts on this app for the foreseeable future.”
Today, for our Enterprise Developer Groups Spotlight series, we go to Argentina where Edgar Glellel founded and runs a BlackBerry Enterprise Developer Group.
Edgar, @turco82 on Twitter, started working closely with BlackBerry since the launch of our first BlackBerry Tech Center in St. Luis, Argentina, where he also founded his first developer group. Through the Tech Center, they started helping local developers and local companies in Argentina to build apps for BlackBerry 10.
At that time, they also started working for a Japanese company for which they built an app called Tazzle it. It’s a service that allows you to quickly share and print content between a smartphone and a PC, through a USB dongle. It’s being used by many companies worldwide and Edgar and his developer group still support that service, but are also busy with some other projects both in the business and consumer market.
Among the others, for example, now that the Amazon Appstore is included in any BlackBerry device, they are helping some local companies to bring their games to that store, but they have also been busy developing the client applications for the social networking site Score and for some other enterprise customers.
It’s great to see passionate developers like Edgar at work, building something very important for their community and for BlackBerry. They have been able to catch lots of opportunities around the BlackBerry platform for over three years, both in Argentina and for other companies abroad and for this reason this definitely makes them a great success story worth sharing.
If you liked this success story, please take a look at the previous ones, too:
Interested to know more about our Enterprise Developer Groups? Do you want to join one? Take a look here to find the one closest to you. If you are interested in starting a new one, instead, please fill this form and we will get back to you as soon as we can.
For developers who are targeting their applications for both the work and the personal perimeter of the device, this might be a million dollar question. Sometimes it becomes necessary to dynamically determine which perimeter the user has deployed an app in.
Needless to say, BlackBerry 10 APIs are designed to be perimeter agnostic. Hence, most app developers need not worry about it. But there are cases when apps need to make decisions based on this. E.g. an app might want to encrypt data only in personal perimeter because work perimeter encrypts all data at rest by default or an app might want to receive configurations from a server based on the perimeter it is in. With that said and understood, let’s take a look at how we can determine the perimeter our application is in at runtime.
First of all, BlackBerry 10 smartphones can operate with multiple, segregated perimeters. There are really only three kinds of perimeter segmentation.
Personal Only – This is a consumer device not connected to a BlackBerry Enterprise Server. There is only one perimeter, personal.
Personal + Workspace – This is a device that is connected to a BlackBerry Enterprise Server. There is a personal section for the user’s personal applications and data (contacts, calendar, files, etc…) and a workspace section for corporate applications and data.
Workspace Only – This is a device that is connected to a BlackBerry Enterprise Server and is operating in EMM Regulated mode. In this mode there is only a workspace perimeter, no personal perimeter.
You can determine which perimeter an application is running in by using a combination of the NET_PPS_ROOT and PERIMETER environment variables.
PERIMETER = enterprise (Balance, Work perimeter) PERIMETER = personal (Workspace Only) PERIMETER = personal (Balance, Personal Perimeter) PERIMETER = personal (Personal only)
NET_PPS_ROOT alone can tell which perimeter your application is in, but combining the PERIMETER variable with NET_PPS_ROOT can reveal further information about the perimeter segmentation type. Let’s have a look at some example use of these two environment variables.
NET_PPS_ROOT = /pps/services/networking/enterprise) would mean a work perimeter – in either Balance or Workspace only.
PERIMETER = personal AND NET_PPS_ROOT = /pps/services/networking/enterprise) would mean a Workspace only device.
..and last but not least, here is an actual implementation of how to determine the perimeter of an application.
I know many will thank me for this post but many will be completely apathetic. That’s good! In fact, I expect most apps should not need this at all and I do not (in any way) recommend tying your application logic to which perimeter your app is in; unless, of course, you have to! Hope this helps folks. Until next time, I will be available @shadidhaque.