Jerry Huang apps and developing apps

Today I'm thrilled to announce that IP CAM Controller for iOS 1.0 is launched for both iPhone and iPad. For those who have iOS device could simply click on this link to download:

https://itunes.apple.com/app/ip-cam-controller/id972015484

1.0 is just a beginning, we are actually working on the next version, hopefully to bring audio and multi-view support in the very near future

Prima dell'aggiornamento di oggi (IP CAM Controller Android v1.8) se avessi voluto effettuare il backup delle tue telecamere, l'unica opzione era di utilizzare la funzione di condivisione tramite un hyper link virtuale una per una. La bella notizia è che adesso potrai effettuare il backup di tutte le telecamere in un sol colpo. Ti mostro come funziona:

 Passaggio 1, seleziona"esporta Camera" dal menù

Ci sarà un messaggio di attenzione, seleziona OK (se sei d'accordo :-))

Passaggio 2. Ti mostrerà una lista di applicazioni abilitate ad inviare il tuo backup, in questo caso, utilizzerò Gmail.

Dopo questo, si tratterà di comporre una classica mail (con Gmail ovvviamente), perfavore notare che tutte le telecamere esportate sono all'interno di un hyper link criptato (alla fine della mail), proprio come un file allegato in formato testo. E' per questo che devi fare attenzione a chi manderai la mail, perchè chiunque abbia il file e la mia app installata sarà in grado di accedere alle tue telecamere!

Passaggio 3: Importare il backup. Aprire la mail, potrai sia scegliere il link nella mail, oppure scaricare il file allegato (per Android versione 4 solamente), il tuo device dovrebbe chiederti come completare l'azione.

Proprio così:

Scegli IP CAM Controller, l'applicazione aprirà un messaggio che ti avvertirà che alla scelta di questo tutte le telecamere esistenti verranno cancellate

Ecco fatto. Le telecamere da un device Android potranno essere trasferite ad un altro! 

Before today's update (IP CAM Controller Android v1.8) if you want to back-up your camera, the only option is to use share function to share your camera via a virtual hyper link one by one. The good news is that now you can backup your camera in the same way but this time you can export all cameras. Let's see how it works.

 Step 1, select "Export Cameras" from menu

There will be a warning after that, tap OK (if you are ok:))

Step 2. Then it will show up a list of apps that able to send your backup, in this case, I'm going to go with Gmail

After that, it just like composing an ordinary email (with Gmail of course), please note that the exported cameras are inside an encrypted hyper link (at the end of the email),as well as a file attachment with your setting in plain text. And that's why you have to be caution whom the email is sending to - because whoever have the file and installed my app will be able to access to your cameras.

Step 3: Import. Open up the email, you can either tap on the link in the email or download the file attachment (for Android 4 users only), your phone should be asking how to complete the action.

Just like this:

 Tap IP CAM Controller, my app will promote a warning to ask whether you would like to proceed, as this will clear out all your existing (if any) cameras.

That's it. Cameras from one phone could be transferring to another Android device just like that:)

It's a known  issue that audio is not working on FOSCAM FI9821W V2 even with the latest firmware. More info could be found on this post:

http://foscam.us/forum/fi9821w-v2-rtsp-via-vlc-working-for-video-but-not-audio-t10025.html

If you are interesting in applying the patch as mentioned at the end of the post above, you can download it here and uploaded at patch update:

http://www.jerryhuang.net/ipcamcontroller/FosIPC_A_patch_ver2.x.1.10_1_20140606_150128_rtsp_audio.bin

I believe this patch will be shipped in future firmware update eventually, so if audio is working for your camera, there is no need to update the patch.

Update: the patch is reported by a Foscam 9821P user that it's also working on 9821P

MSFT is about to rolling out the gorgeous WP81 update - the biggest and the most important upgrade in the history. And that is a nightmare for most app developers like me

First of all, for those who are having trouble with the title of this post, please kindly click here for translation. I just couldn't find a better title than that and it's time for you guys to learn some Chinese, LOL

When I upgraded from WP7 to WP7.8, I don't have too much trouble and of course less excitement - it was nothing but adding a socket (to some extend:). When it came to WP7 to WP8, I was excited because C++ is available and the app finally support audio. I have done a lot of coding at that upgrade but mostly about new functionalities - I don't have to rewrite everything.

Now, things are getting more complicated and it looks like there isn't much benefit I could have (neither the app user). There are 2 options to upgrade the development from WP8 to WP8.1, let's start with a nice comparison: http://msdn.microsoft.com/library/windows/apps/dn655121(v=vs.105).aspx

There are actually 3 options in above article but option 1 (not upgrading) is out of the table as we want to move on and believe me that's the last option MSFT ever want (they put huge money on the new WP81 but telling you to hold off, no way!).  For the other 2 options let's read a discussion I found here: http://social.msdn.microsoft.com/Forums/windowsapps/en-US/bf855b7f-d7ca-4b73-964f-22ac77f7d4c4/benefits-of-windows-runtime-over-silverlight-in-wp81?forum=wpdevelop

To simply put, there are 2 different WP8.1 in terms of development framework, one is Silverlight 8.1 (SL8.1) while another is Windows Runtime (WinRT, aka Universal app). The latter one is the same framework when you develop a Win8.1 store app for Windows tablets and/or W8.1 desktop (Metro). Although MSFT claims that they are equivalent about everything, the truth is that WinRT (universal app) is being seriously promoted right now while SL8.1 in my opinion is something intermediate during the transition (remember WP7.8 before WP8, sound familiar?).

If I predict above correctly, RT is the future for app development (phone and tablet) on Microsoft's platform, therefore in long term I would like my development to be on that. However, it really means to rewrite the whole app again - not everything, but still a lot including the UI. And it becomes more trouble if your projects have reference to 3rd party libraries (which is very common for even a small project) - they need to upgrade to support that as well.

When I say "including the UI", I mean:

1. This only apply to WP8 -> WinRT upgrade path
2. XAML is not reusable, because the UI framework are different between WP8 and WinRT, you may consider things are being rewritten/re-design in WinRT.
3. There are a lot of UI controls available in wp8 have gone or being replaced. such as LongListSelector (replaced by GridView or ListView or maybe something else), <controls:Pivot> becomes just <Pivot>, etc
4. If you are porting your WP8.1 app from a Win8.1 app, and if you use lib like WinRT XAML Toolkit, you need to find alternative or wait for future update from the component developer because currently doesn't support WP8.1 just yet
5. If you are upgrading from a WP8 app, and if you use lib like Coding4Fun toolkit, similar to above, you have to find alternative or wait for update because current version doesn't support WP8.1
6. Don't forget doing so much will not bring any improvement or new feature to your users, instead, it's very likely to cause some bugs as the changes are about everything: UI, API, etc

So what if we go with SL8.1 as MSDN suggests just some changes? It's much less painful (above item 5 is also applicable though) but keep in mind that WP8.1 is new, you might still have a lot of users on the old platform and so you need to maintain development on 2 platforms (if you care those users). As a result, you will have to clone a new set of projects (including the UI project) from your WP8 solution (you will need linked files); and re-target the new projects to WP8.1. After that, any change, especially on the UI, you are likely to code twice. This kind of maintenance will last for a while base on my experience, until WP8 is completely or almost fading out.

I haven't completely decided yet how to upgrade my development for my app, for now, I would rather just sit tight and watch

A new cool way of controlling your camera had been introduced in the latest updates: sensor mode. After turning on the sensor mode, the app will use your phone's Accelerometer Sensor to detect which direction you are tilting and so trigger a Tap to Center (or Tap to Move if your camera doesn't support TTC) command.

Tapping the "direction" button to activate sensor, hold your phone horizontally, then tilt to a direction the camera will move toward that. The above video is using WP8 as sample, the feature is working the same way in other platforms (Android, WinRT). In android, to activate sensor mode, should tap the "compass" icon instead:

This is actually interesting and it extends a lot of possibilities. Imagine that you can put your phone on something constantly shaking and so trigger a random patrol on the camera. Another idea which I haven't think it through is that if you have something more advanced like a robot-car, so that your robot could somehow control another camera.

With latest update for WP8 (v3.3.5) and WinRT (v1.3), a camera setting could be shared between these 2 platforms, with either a link or a file attachment. See follow scenario as a sample:

On your tablet, activate bottom command bar in single view screen, then choose "Share via File" (or Share via Link if you like)

A share charm will be showing on the right hand side:

Choose Email to send the file in email attachment; In fact, if you had installed other app with file-sharing ability, there will be more options there.

After that, just like sending a regular email, you can type in extra info for the recipient. Just don't forget to tap the "send" button on the right upper corner:)

With IP CAM Controller installed on recipient's phone or tablet, simple open up the attachment, IP CAM Controller is able to read the encrypted content from file and open a view screen immediately. With this approach, the recipient doesn't need to input any configuration about your camera (such as IP, port, credentials, etc), they are all inside the small file you sent over.

Note for using "Share via Link"

The share by link is working similar except that the camera info is inside a hyper link (aka deep link). The link following this format:

ipcamcontroller:view?v=4&cam=xxxxxxxxxxxxxxxx

There are 2 critical parameter here:

v=4: version is 4 which is the newest version number by far;

cam=... : for different version, it works quite differently. For version 4 specifically, it's a shorten URL like http://goo.gl/abcdefgh; for version 3, the cam value is a very long string which normally over 600 characters;

The phone version supports all versions while the WinRT only support version 4.

For those who are interested, tap following link to download the new app:

http://apps.microsoft.com/windows/app/ip-cam-controller/a9410b30-4b50-4e98-9783-c525895eba1d

some snapshots: