PowerArchiver 2012 or PowerArchiver 2013


  • conexware

    PowerArchiver 2012 or PowerArchiver 2013

    As we work on next generation PowerArchiver, we face difficult decision we often do - how to name it.

    Last time we started beta’s in March and completed final in late July, and we called it PA 2011 - mere few months later, it seems as if it old product.

    So what do you think we should name next one - PA 2012 OR PA 2013?

    thank you!


  • conexware

    Just to remind everyone, this has nothing to do with the product itself or update terms (business users will get same update no matter what it is called), it is pure marketing term and thats how it should be looked at.

    thanks!


  • Alpha Testers

    Doesn’t that depend on the year of release or am I missing the point there? (No I don’t understand marketing). 😃

    It would seem odd IMO calling it PA2012 if if was to be released in 2013. Likewise if it’s released in 2012 it would seem odd to me to call it PA2013.

    For that reason I selected 2012 in the hope that we get a release sooner. 😉



  • Ok,

    If it was me, and based on what i know if i were working with or for Conexware as employee or business advisor.

    I would suggest that if all of the below services, features and applications can be completed to RC1 standards by October 2012 then we i would do PowerArchiver 2013 for pulic release testing and aim for Final by January.

    1. PAF format
    2. ZiptoEmail
    3 AttachmentCloud
    4. Conexware - Wiki Support Site
    5. Patche’s, Improvements & Bug Fix’s with PowerArchiver

    If you can deliver all of the above before May then you could do 2012.

    Personaly, i would like to see all of these new features, services available at once with the release of a new 2013 Application.

    I would like to have the cloud, zte both finished as a joint project. not zte 1st then cloud after.

    with the new PAF format i would like to see this in a major update ie 2013 along with enhancments we have discussed in alpha chat.

    As always, it depends on resource and how far you are on things like Wiki, PAF and ZTE. Cloud services can be dulled down to a part and then improved on over time if required as its a web service.


  • conexware

    Nice input fellas!
    I think that this is unrelated to ZTE, as it will be a software separate from PA.

    In terms of 2012 or 2013, say we complete all the great features (&more maybe) in May/June and that would, depending on the official release date, give only about 6 months of PA 2012 actually being in 2012. Then what?
    With that, I think PA 2013 would give a better advantage marketing wise as it will give an impression to current and potential customers that we’re constantly working ahead and moving forward while the new and evolving features in PA will justify that perception.


  • Alpha Testers

    @Mili:

    Nice input fellas!
    In terms of 2012 or 2013, say we complete all the great features (&more maybe) in May/June and that would, depending on the official release date, give only about 6 months of PA 2012 actually being in 2012. Then what?
    With that, I think PA 2013 would give a better advantage marketing wise as it will give an impression to current and potential customers that we’re constantly working ahead and moving forward while the new and evolving features in PA will justify that perception.

    That’s a good enough explanation as to why 2013 would be preferable solution Mili.

    Makes sense when you put it like that. 🙂


  • conexware

    as mili said, ZTE/AC is completely separate and first beta will be out soon Richard… PAF wont be there for another 6-10 months at least, lots of work.


  • conexware

    Tx Luxor!
    Keep em coming folks! 🙂



  • I would prefer conexware to go from 2011 to 2013 to be honest, i think i made that fairly clear. it all depends on what is actually being done in the background.

    Obviosly, you dont tell us everything that is going on so all i know is what is listed and bits inbetween during testing.

    ZTE is a seperate application i understand. But it also uses cloud service which is very new and in trial stages if that takes longer to setup than ZTE then would it not be best to release it togeather thus giving more time for testing and tweaks.

    It all depends how quick you want to make the cash on that app.

    But its you company, your plan.

    I hold no weight in your deciding factors, i mearly aid when asked too and offer my thoughts from time to time.


  • conexware

    basically, is it weird to call something 2013 when it is released in May, or June or July 2012?


  • Alpha Testers

    @spwolf:

    basically, is it weird to call something 2013 when it is released in May, or June or July 2012?

    If it is released in these months then yes I would say it’s weird to call it PA2013. But as Mili says that only gives you 6 months to play with then you are into 2013.

    So in a marketing viewpoint PA2013 makes more sense.

    Guess that’s the problem with tagging on the year when naming PowerArchiver versions.

    Maybe you should just call it PoweArchiver 13 and drop the 2000 part altogether. 😉 😃



  • Well, why not harmonize with the version numbering?

    So PA2012 - PA 12.5.xxx
    (e.g. maybe an update with only PAF)
    For May/June.
    PA2013 - PA 13.xx (all the good stuff)
    For Dec/Jan.


  • conexware

    @TBGBe:

    Well, why not harmonize with the version numbering?

    So PA2012 - PA 12.5.xxx
    (e.g. maybe an update with only PAF)
    For May/June.
    PA2013 - PA 13.xx (all the good stuff)
    For Dec/Jan.

    year is only marketing term… version number shows how many changes there were. but yeah, something like that was what I was thinking…



  • I’m not disputing the 2012/2013 bit of course it would be 2012 if it was released this year, but if was around october you might as well make it beta 2013.

    Again, it depends on at what point you are to make the choice. is pa at a point where you could release a major roll out.

    Personally, PA works great as it is, i see no reason to rush development this year. unless its to resolve bugs i dont mind waiting till next year.

    We have ZTE, Cloud and Wiki to keep us all busy.

    @Luxor:

    Maybe you should just call it PoweArchiver 13 and drop the 2000 part altogether.

    I like that idea!! get rid of the year all togeather, why not make 2013 not only a modern improved version but rename the version to PowerArchiver 13.0



  • Or get rid of Numbers altogether !?
    What about "PowerArchiver Niburu ";)



  • @TBGBe:

    Or get rid of Numbers altogether !?
    What about "PowerArchiver Niburu ";)

    Not to sure about that fella :D!

    However, its a good metaphor for what PowerArchiver might do to our Competitors… Wipe them out! Boom 😃


  • conexware

    PowerArchiver NXT
    PowerArchiver X
    PowerArchiver Destroyer/Nibiru

    hmmm

    🙂



  • oh dear, we are off track again.

    Ok, i will make the deciding factor. 🙂

    A mid update for 2011 will be brought out containing current patch’s, minor bug fix’s and enhancments.

    ZTE, Wiki and PAF will remain in development during this year and tested by the development team and us highly skilled alphas! 😉

    PowerArchiver title will adjust taking out the year. thus keeping version number much like many other brands.

    The cloud service will be a job to look at when ZTE has reached a stable version with all major bugs resolved. This means we can focus on testing the cloud service more than the application.

    🙂 Well thats how i would manage this process.


  • conexware

    Wiki will be in next PA for sure, not waiting for end of year… and few other things too :-).



  • Great on the wiki thing! because its a great tool to have. also updates can be made without local downloads to each user client.

    There are a few things i am keen for;

    1. ZTE
    2. PAF Format
    3. Developer Tab [the custom tab] no confirmation if you are looking at it but if that is a v13 update thats fine by me 😃
    4. Cloud

    the cloud thing isnt a major for me because i already have cloud services such as LiveDrive and Box. both with windows shell extensions and share to user abilities.

    However, that doesnt mean i dont see the advantage for Conexware to go down the route. I do remember sending an email over a year ago to you drazen suggesting such a feature and you replied saying it was on the thinking board already.

    “great minds think a like” 🙂



  • Maybe call it “New Powerarchiver”? Or is this just stupid?



  • @guido:

    Maybe call it “New Powerarchiver”? Or is this just stupid?

    :rolleyes: ……



  • As some may have already stated (did not read entire post) the next version should be 2013. By the time testing is finished and it’s released to the public, it’ll be late 2012. Most not familiar with PA may assume it’s an older version and may bypass it for a competing product. 🙂


  • conexware

    @Sir:

    Great on the wiki thing! because its a great tool to have. also updates can be made without local downloads to each user client.

    There are a few things i am keen for;

    1. ZTE
    2. PAF Format
    3. Developer Tab [the custom tab] no confirmation if you are looking at it but if that is a v13 update thats fine by me 😃
    4. Cloud

    the cloud thing isnt a major for me because i already have cloud services such as LiveDrive and Box. both with windows shell extensions and share to user abilities.

    However, that doesnt mean i dont see the advantage for Conexware to go down the route. I do remember sending an email over a year ago to you drazen suggesting such a feature and you replied saying it was on the thinking board already.

    “great minds think a like” 🙂

    i recently went through my logs and found first time talking about something similar to AC was 2007 🙂



  • PowerArchiver Reloaded


  • Banned

    Rather than shoot a major release every year, why not just say: every two years. Then make sure that it is a MAJOR release.

    Quite frankly, I find it annoying with companies feel compelled to do something every year, when the differences between any year (or even every two years) is relatively slight.

    In my mind FF hurt themselves when they stopped waiting 3-4 years for a major release, and started issues new releases every few months.



  • @Socrates:

    Rather than shoot a major release every year, why not just say: every two years. Then make sure that it is a MAJOR release.

    Quite frankly, I find it annoying with companies feel compelled to do something every year, when the differences between any year (or even every two years) is relatively slight.

    In my mind FF hurt themselves when they stopped waiting 3-4 years for a major release, and started issues new releases every few months.

    I partly agree with you on that one!

    However, the users doesnt have to update their system.

    Also, with patchbeam you can set it up so it update’s when you want it to without any anoying messages.

    And Programs that require Driver’s, Codecs or definitions such as Media Streamers, spyware or antiviru’s software always recommended you download the latest updates.

    For powerarchiver having the knowlege that you can compress using the latest compression formats currently available while keeping it backward compatible is a major plus point.


  • conexware

    @Socrates:

    Rather than shoot a major release every year, why not just say: every two years. Then make sure that it is a MAJOR release.

    Quite frankly, I find it annoying with companies feel compelled to do something every year, when the differences between any year (or even every two years) is relatively slight.

    In my mind FF hurt themselves when they stopped waiting 3-4 years for a major release, and started issues new releases every few months.

    this is what we have done in past, major updates are on average done within 16 months.

    and this is also why we developed patchbeam, to make them simpler and easier so we can do more of them.

    that way when you tell us you want feature like solid compression in batch converter, we can do it within month and not 2 years.

    with new format though, updates will come on monthly basis, thats the only way development can work when something is brand new.


  • Alpha Testers

    @spwolf:

    So what do you think we should name next one - PA 2012 OR PA 2013?

    thank you!

    My suggestion is that you skip the year in the name PA. Instead you use YY.MM as name when the actual version of PA is released.

    Example: If the next version is released in May 2012, then name it PowerArchive 12.05. If it’s released in Feb 2013, then the name will be PowerArchiver 13.02. By doing this you can then simply by looking at the name know what year and month the actual version of PA was released.

    You can also have the internal version number in the About Box. Something like PowerArchiver 12.05 (13.00.10) or whatever the next version will be.

    Kind Regards
    Micke



  • @Luxor:

    Maybe you should just call it PoweArchiver 13 and drop the 2000 part altogether. 😉 😃

    I was just going to make this suggestion.

    Way back in 1995 Microsoft started this “name the product after the year it came out” convention & then Norton (and lots of others quickly followed). You’ll notice that almost all of them have abandoned that method of naming for more conventional methods.

    My guess is for the reason SPWolf voiced…once it becomes a new year your product sounds ‘out-dated’ even if it came out just a couple months before the calendar change.

    I vote for PowerArchiver v13.0. Prominently displaying that the program is in its 13th major version shows that it is a very mature piece of code that’s been around a long time and trusted by its users.

    Naming it something like PowerArchiver 2012 or 2013 really doesn’t reveal anything about how mature/reliable the program or the program’s roots.



  • 2013 all the way 🙂


  • Alpha Testers

    @Innuendo:

    I vote for PowerArchiver v13.0. Prominently displaying that the program is in its 13th major version shows that it is a very mature piece of code that’s been around a long time and trusted by its users.

    The version number don’t tell the user how old the current version is. Instead I suggest you skip the version number in the name and instead use YY.MM in the name. That way the name will tell you how long the current version has been released.

    Naming it something like PowerArchiver 2012 or 2013 really doesn’t reveal anything about how mature/reliable the program or the program’s roots.

    You can say the same by using version number. The version number doesn’t tell you anything about how mature/reliable the program is. Example of this is Inkscape that has version 0.48, but is a very mature and reliable program. On the other hand, Firefox release a new version number every 6 week, but that doesn’t make the program more mature.

    The point is, version number don’t matter and therefore don’t have to be part of the software name.

    Kind Regards
    Micke



  • I agree with Luxor & Innuendo - I think removing the year would be a good move, and give it a version number. A version number does not make the product feel as dated, nor does it then tie you to a specific release date etc. 🙂


  • conexware

    thanks for everyone’s input!!!



  • So what’s the verdict?



  • PowerArchiver 2012 Part Duo will be released next month.



  • i would prefer the date and the version number so people can see when the product was released.



  • @davidsplash:

    i would prefer the date and the version number so people can see when the product was released.

    You can check that in product history, via blogs, and in the help file. 🙂

    At the end of the day, its no Biggy, but it seems more users are happy for it to move with a build identifiy rather than a Year.

    You only have to look at our Competitors Winzip, Stuffit, 7-zip,Winrar.

    All of such moved away from Year stamps, as it doesnt really give the user an indication of major, minor, revision updates.

    Every time i visit Winzips website i know prior it was version 14.1, i visit the site 2 months later its 14.6. instantly from that i know changes have been made without having to read the news, blogs or anything else.


  • Alpha Testers

    @Sir:

    Every time i visit Winzips website.

    :eek:Traitor!:p



  • lol, many of my suggestions that have been put into PowerArchiver were from checking out our competitor’s and other software products.

    It’s all part of the job. But rest assure, i have never purchased Winzip, nor do i have it on my system. it is powerarchiver all the way.

    I do however, install winzip every 3 months play with it and compare it against PA. then uninstall.


  • conexware

    @Sir:

    You can check that in product history, via blogs, and in the help file. 🙂

    At the end of the day, its no Biggy, but it seems more users are happy for it to move with a build identifiy rather than a Year.

    You only have to look at our Competitors Winzip, Stuffit, 7-zip,Winrar.

    All of such moved away from Year stamps, as it doesnt really give the user an indication of major, minor, revision updates.

    Every time i visit Winzips website i know prior it was version 14.1, i visit the site 2 months later its 14.6. instantly from that i know changes have been made without having to read the news, blogs or anything else.

    You see build number of PA everywhere, on main page, on download page, on download.com everywhere.

    It is not like it says PowerArchiver 2015.

    It is PowerArchiver 2011 12.12.


  • conexware

    And thanks for everyone’s input.

    If we developed our software as rarely as competition then we not use the year :P. But we do. It is also basis for our upgrade schedule so it wont change anytime soon.


  • conexware

    @guido:

    So what’s the verdict?

    2012 soon!



  • My vote is to call it PA 2012 or 2013 (year), then the build number like you have eg 12.12.

    By the way, some new 2013 cars are out already eg the Maxda CX5 🙂 For atleast a month already…

    By the version date, eg 12.07 (eg July) vs 12.09 (eg September) it is hard to tell if there is a major change, eg from PA 2011 to 2012 with, thus the PA 2012 is still necessary. Hopefully you get the idea, to still keep the PA 2012 versions.

    Keep up the great work Conexware team!



  • what you dont want is to change the version numbers widely. I would suggest that you yuse the above suggestion say 13 for year and mm for month and a b c or d for the version numbers for that month if you need bug fixes that month



  • I like the old style. Just use the real version number.
    v13.xx

    I don’t like the year number which always make confuse and bad if your don’t big update in those year or up coming year.



  • Why don’t we try to get rid of the numbers?In my opinion Power Archiver neo/beta/Alpha sounds cooler then Power Archiver 2012 or 2013!!



  • @Johnmoglas:

    Why don’t we try to get rid of the numbers?In my opinion Power Archiver neo/beta/Alpha sounds cooler then Power Archiver 2012 or 2013!!

    Using “Beta” “Alpha” are typical stages of development and you have them in every version developed.

    And technically we do PowerArchiver - “Profesional”, “Legacy” and “Toolbox”.

    Having Version numbers are really helpfull as it can give you an instant idea of the age of the product when you visit the site.


Log in to reply