Thread: iGO Primo vs Nextgen.

You don't judge NextGen on its look/layout because all of that is flexible via skins (that is what makes NNG great.) You judge it on performance and capabilities. NextGen is young and skins are still evolving and problems are being fixed. Earlier release of NextGen was slow on start up and slow on running (even on devices with good CPU and memory) NextGen "new architecture" eliminates the "resolution" settings which was painful to deal with on different devices. Also the dpi settings allows high resolutions to work while iGO/Primo depend on discrete resolution data (320x240,480x272,800x480,etc...) Android devices with resolution as high as 1080p are taking over and you don't find many WinCE devices with resolution greater than 800x480; using Primo on it via 800x480 data is sad.

Certain latest release of NextGen is quick on startup, has some zippy responses and skins are getting better. The "ux" way of adding additional capabilities and not keeping skin in one file makes it difficult for people to get it working (because they mixes them up) and hard to debug (because no one know where they comes from and use for.) But then NNG didn't create NextGen for hacker to enjoy nor users to steal from; it's for their branding of different vendors they sell to. The NextGen looks and feels are designed to be similar (and somewhat bland*) across different car Nav system they are part of. When comparing keep in mind what the original default skin of iGO/Primo/NextGen looks like. Don't get confused with skins such as dimKA, Doupas or Pongo and how they change the looks (for better or worst) and what additional capabilities they provided. Compare apple with apple!

* hard to have a "professional" look with a rainbow of colors sparkling all over