Posts tagged improve
Today, during Ontario’s Civic Holiday, I finally got around to filling out Deloitte Technology Fast 50™ CEO Survey. There was an interesting question that sparked a thread that I’ve been thinking about lately:
“Specifically, do you think the SR&ED tax credit program is pretty good as is, or needs improvement? If it needs big changes, what would be the first change you would make?”
For those of you who don’t know what the SR&ED program is, go learn more because it can save your business tons of cash over time and help you finance your business with non-dilutive government assistance.
For those of you running (or have previously run) early-stage stage startups, here are my thoughts: Currently SR&ED will refund a portion of a startup’s R&D costs based on expenses incurred during the previous year – some of those earliest expenses claimed were incurred 18 months prior to the claim. For startups, this is an eternity. Today, startups can grow and die violently before they get their first SR&ED claim, which could have helped them to pay one more employee, solve one more problem or help one more customer.
The Canadian government should consider modifying the SR&ED program to include a faster-reimbursement timeframe for startups (making less than $1,000,000 in revenue per year). For example, this could mean making claims quarterly and being reimbursed within 60-90 days – this would massively improve startup financing in the short-term. A modification, as requested, would help startups build value and growth potential more quickly and help the overall competitiveness of the Canadian technology sector.
Will anyone help to stand behind an initiative to get the Canadian government to improve the SR&ED program for startups? Join the conversation in the comments below.
I briefly touched on application stores as part of my last post, Creating a Better BlackBerry Experience. After re-reading the post and reflecting on some of the comments, I felt that a more in-depth follow-up was required to discuss why the overarching design of a mobile application store is paramount to its adoption, usability and ultimately, success.
This post will focus on how I believe the design of BlackBerry App World (“BBAW”) can be improved for both enterprises and consumers.
BlackBerry App World for Enterprises
When BBAW was first released, many BES-connected users had problems downloading applications due to permission-based issues. RIM can’t do much to change corporate policies, but RIM can implement a highly-anticipated BBAW for the enterprise. I am proposing that RIM creates an enterprise app store, similar to the app store announced by MobileIron in December 2009. MobileIron’s enterprise app store allows enterprises to create a repository of approved content and apps, which employees can then download and use with the full blessing of IT. In addition, an enterprise can create device or employee categories with permissions for certain types of content. As mentioned by Kevin Fitchard of Connected Planet, “Salesmen, for instance, would find Salesforce.com’s app in their approved storefront, while a field engineer would not. Both field engineers and salesman could have access to vehicle navigation services, and while a desk jockey might be able to download that same application, the company could set usage restrictions limiting when he or she could use it (say, business trips) or require the employee to pay the monthly service fee in a separately generated bill.” To me, this concept sounds like an app store that would help RIM sell more BlackBerry devices to enterprises, help IT administrators and make employees more productive (and happy) when mobile. Obviously, a more tidy billing mechanism will have to be in place, since I’d reckon the majority of enterprise won’t want to pay via PayPal.
BlackBerry App World for Consumers
In creating v2.0 of BBAW, RIM has a lot of work to do. My last post discusses a few elements that need improvement including the billing systems, pre-loads and fewer bugs. I’d like to add a few more points to the discussion. To begin with, the billing system needs to be more dynamic and allow customers to attach credit cards to their profile for frictionless billing. The billing systems should also be flexible enough to power additional business models for application developers including subscription billing and in-application micro-transactions. Why not bring the minimum price-point to $0.99 as well?
Steven Berkovitz chimed-in to mention that with BES 5.0, there’s a full-blown web version of desktop manager; it uses an ActiveX control to connect to your Blackberry for operations requiring a physical connection and personal data is sync’d over-the-air (“OTA”). However, this functionality doesn’t yet extend to previously installed, licensed and configured applications. As a consumer, wouldn’t it be nice to buy your next BlackBerry, insert your SIM card, load your user profile from within an OTA-driven application and click “Restore Profile” to then have your data, applications (auto-detect new BlackBerry OS and download proper build for the new device) and configuration settings loaded onto your new device OTA? That is one step towards a BlackBerry device that can compete with future iPhone models in delivering the experience sought after by the ever-smarter and bells-and-whistles-seeking consumer today.
Many users are also confused by not being able to find certain apps in BBAW that show up for their friends or colleagues. By design, RIM only shows its users the apps available for their device. In a future version of BBAW, it would be nice to show users all the apps and allow users to be notified (by push, email, SMS, etc…) when the app is launched for their specific OS and device model. This could also give developers a sense of what devices are generating the most demand for their product so that they could focus their development efforts on the makes/models and locations that are going to yield that greatest financial rewards or user adoption.
BBAW needs to come pre-loaded on all (new) handsets. End of story. In cases where mobile carriers have a contractually dominant position over RIM on controlling content or applications available to mobile devices, RIM should provide those carriers with sufficient access and privileges to formally reject specific applications for use by their subscribers for their own reasons. In concert with these changes, RIM should enter into a formal revenue sharing agreement with carriers so that revenues generated from application one-time sales, subscriptions and micro-transactions can be shared. Once these deals are signed, RIM (or the mobile carrier) should push App World down to all BlackBerry devices. IMHO, this would be a win-win-win scenario for RIM, carriers and consumers.
If you were RIM, how would you design BlackBerry App World v2.0?