Database Users

Could an XDA II do this?

Would it be possible and within an XDA II's hardware limitations to run a fullscreen video with multiple sprites overlaid? Possibly with transparency and other little effects?
Again, thinking of a game...

Is it a waste of time making games for the ppc?
I mean, I've worked on games before and I'll bet with some help I could make some nice ones, but when selling at $5-$10ea will it generate enough sales to be worthwhile?

if you need inspriration look at games like the
quake1 and 2 and dukeNukeEm3d ports
and warcraft2 and others as to whats possible
if you can make money on it i have no idear
there are tons of good free ones
though many people feel that playing on pda's is a hassel

I don't need inspiration, I've plenty of ideas and I think they'd be alot less hassle than playing something like doom on a ppc. But what are my chances of finding some programmers to write the game for next to nothing, since that's probably the kind of revenue ppc games make.

i were not speaking of inspirations as to what the game would be about
but about what would be expected of the speed and abilities of the platform
may also want to look here
http://pierrel5.free.fr/PocketGLb/ReadMeFirst.htm

Importance of Group Playtest for Game/App Development

Digital Eclairs went to Pinewood's after school program called AppLab, focused on getting kids more hands on on new electronics coming up.
We presented our project XnO, with multiple handled devices to kids (age group 8-12). After the first 15 mins of hands on experience, they were really enjoying the gameplay, comparing it to different games titles and how it was better, why they liked 3D, asking questions on when the app would be released, and they were very interested in knowing about the process of how it was created.
It showed us that 3D environments were a welcome change, kids respond well to warm colors we used. We set each kid on a different level and they seemed comfortable playing and getting familiar with the app. Some kids responded very well with the higher levels and some not so well because we had not ramped them through the initial gameplay, but after a few tries they started to get the hang of the game and when they were able to win they were really happy. In retrospect we realized that this was a bit of a difficult learning curve for someone new coming to this game, but with the release upon us we had to move forward with what he had. In order to give people a taste of the game on the iOS we released with a showcase of 5 levels, which looking back on it now, care is needed when choosing the level of difficulty to the casual gamer.
The Accelerometer presented an interesting challenge to the kids, once they figured out they could lift the device and tilt it left and right to move the character they were able to pick up on it quick and continue with how they had been completing the levels previously. We were short few devices and a few kids had to share the same device. The ones who were collaborating did very well on higher levels taking turns and really engaging in the game and helping each other and were faster in adapting to the game. This helped us understand that putting out a physics puzzled based game would definitely require a walkthrough to help the community through some of those tough levels.
As a developer with our first game a week away from release, it was an exhilarating experience to see our product being enjoyed by these kids. Their eagerness to explore all the game features gave us so much satisfaction and all the pain and efforts in building this game were totally worth it. The kids were very interested in knowing the process of how the game was made and when they were asked for feedback they all jumped in saying: They loved double headed turtle and wanted a three headed turtle, in-game currency that they can use to buy in things in game like weapons, wallpaper, and many more suggestions.
To anyone who want to make their own game, arrange group play tests ahead of time once you have a working build. You will get wonderful insight into your game. We had initially done a lot a individual testing from industry people, which is very useful and should not be ignored but for a complete overview on a game and end user perspective go for group tests, as individual test can sometimes be misleading. And do it as soon and as often as possible.
Digital Eclairs, is an independent game development studio. XnO - 3D Adventure Game is launch on iTunes and Google Play.

How-To White-Box a Game (Making of XnO Part II)

No story is complete without its origins. We love to share with you the very first white-box environment of XnO!
XnO began its origins from the name "Ice Breakers", the way the cylindrical blocks were breaking. We had 3 walls couple of boxes from unity asset packages. And began the journey. We wanted to take a simple idea and implement in it all the possible depths.
When we began majority of the games were 2D or side scrollers, that never gave the player full satisfaction of real life interaction with physics of the objects. So we chose a 3D engine, as to why "unity" - the amount of tutorials, community support and ease of start was a key factor in choosing that engine.
To be a team you would need atleast 3 components to begin with - programmer, 2D/3D artist and level designer. Not to say one person can handle more than one aspect. As a team we were all on the same page, we want to make a physics based game with focus on gameplay first.
We followed the following steps:
i) Create first level - We used very basic components - rectangle, sphere, cylinder to create a game play scenario.
ii) Create a flow through of the game - Main Menu, Options and Level Select Screens. Once this was done adding new levels was very easy.
iii) In Game HUD - To enter and exit from any level
iv) Uploaded a web version for our friends/family to play.
Once we had all the pieces then we focussed on exploring all the possible depths and variations in the gameplay that can be achieved to make the game engaging and fun. In our case - target variations, introducing obstacles, power-ups, use of accelerometer to enhance gameplay. Once we had built the key features in, we explored on how to increase difficulty of the levels as the game progressed. At this stage we made some of our models, used some from unity and still used royalty free music.
Once we had good 20 levels working with all the above, we started showing it to people who either played a lot of games or were in gaming. This gave us a good insight on how improve.
As an indie developer it was so much easier for us to do the white-box the way we did because we focussed on Gameplay and Game Design, not so much on the art in the beginning. So when we got the feedback to change, it was so much easier to do it. We were never set in stone.
XnO is our attempt at making a 3D game with as close as possible to real physics without sacrificing the gameplay and memory footprint of the game. XnO is now available on Google Play and Amazon App Store.

idea to make a new android dev board

Hello!
I'm working on a very ambitious project and I thought i'd reach out to see if anyone here at xda would have some comments.
I detailed the basics in this reddit post:
http://www.reddit.com/r/SideProject/comments/2pqh3f/an_idea_to_end_the_proprietary_living_room/
TL/DR: I want to make a new embedded dev board (like a raspberry pi) but with more power, and HDMI Inputs, and HDCP Compliance. This dev board would be the heart (brain) of new open source AV Receivers.
I want to target linux, as well as Android with this. I think an Android powered AV Receiver would be AMAZING!
Currently i'm leaning towards an atom processor, as the price is right, and the performance seems to be very good. x86 development is very mature, however that could prove a hindrance, as arm is more optimized. However, i'm sure others have insight into the ideal configuration. I haven't used the nexus player (only x86 device i know of), so i'm interested in hearing peoples experiences.
I welcome all questions and comments. I'm looking for someone interested in helping with the design of the board.
The Open Home Alliance
Freeing humanity from the proprietary living room
Coming soon to other rooms...

OXY SmartWatch Preview

Hi guys, I am the owner of OXY SmartWatch, a new SmartWatch available in two versions: Round and Square.
Here a few preview renders of our final product:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
This is our website:
http://www.oxytechs.com/
And our Google+ page where you can follow our progresses:
https://www.google.com/+Oxytechswatch
The watch is running Android 4.4 AOSP and we have built a custom version of Android that is more feasible for SmartWatches than Android WEAR. Plus we have custom Android Studio templates to work with our product and we give the possibility to install any ROM without breaking warranty or support.
In this thread I want to share with this community a preview of the Watch and our links.
We are also looking for Android Developers, Android Kernel Developers and iOS Developers.
We also accept candidates from remote locations so feel free to share with us at info[at]netarchitectures[dot]co[dot]uk your resume or feedbacks about our product.
If you want to join our Developer Program, follow this link:
http://forum.xda-developers.com/android/software/oxy-smartwatch-development-t3185452
The watches have:
CPU MIPS M200 Dual Core
512 MB RAM
4 GB Disk Space
Heart Rate Sensor
Vibration
AMOLED Touch display covered with Gorilla Glass
Speakers and Microphones
Magnetic contact charging mechanism
Gyroscope, Accellerometer and Magnetometer
Bluetooth 4.0 and BLE Compatible with iOS and Android and PC
Light sensor
400 mAh LiPo Battery
72 hours with BLE and 1 week without Bluetooth enabled
Stainless steel IPV6 water proof
Right now we are working at our website www[dot]OXYTECHS[dot]com and for the end of August you will be able to see the full product description, accessories and various demo.
The 15th of November 2015 we will open the PRE-SALE Campaign.
We have a batch of 5,000 pieces available per model, so a total of 20,000 pieces:
5,000 Round Stainless Steel
5,000 Round Black Stainless Steel
5,000 Square Stainless Steel
5,000 Square Black Stainless Steel
This project is related to the porting of IWOP (Ingenic Wearable Open Platform) for OXY SmartWatches.
The platform IWOP is available here for download: http://iwop.ingenic.com/.
OXY is giving hardware development kit to each developer who is willing to contribute to the platform.
Attached to this thread there are architecture views, UX mocks and interaction design about the OXY custom ROM.
More details related to OXY are available here: http://www.oxytechs.com/
OXY ROM is composed by:
A watchface manager
Home launcher
Control manager app
Settings app
Apps navigator
A set of utilities apps delivered with the product
XDA:DevDB Information
OXY SmartWatch V 1.0, ROM for the Android General
Contributors
raffaeu
Source Code: http://iwop.ingenic.com/
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.10.x
Based On: IWOP
Some preview videos of OXY ROM:
Notifications Manager
Watchfaces Manager
Phone Calls Manager

Only IPx6, multiple (more than 3) actions to access key info and apps for "Probably 249 or 299"? Hard sell, even with custom ROM support.
On the square version, a bezeless display is easily possible if the PCB and battery are not larger in area than the display area.

Lokifish Marz said:
Only IPx6, multiple (more than 3) actions to access key info and apps for "Probably 249 or 299"? Hard sell, even with custom ROM support.
On the square version, a bezeless display is easily possible if the PCB and battery are not larger in area than the display area.
Click to expand...
Click to collapse
Hi Lokifish and thank you for your feedback.
The answer you mention is about the Black version, which is full Black Stainless Steel, including the wristband. Consider that only the wristband has a production cost of 28$ (without VAT) the price of 249$ does not look that bad to me. Think about OLIO SmartWatch, it's a full Stainless Steel watch with locked ROM and it's sold for almost 600$ a piece.
About the square version, we couldn't find ANY manufacturer in Taiwan, China and Singapore capable to produce a full baseless square display, only round can be baseless but if you know any manufacturer capable of making AMOLED display squared with Gorilla Glass I would be more than happy to get your help, we are still in the beta version of our product and any feedback is welcome and well appreciated.

The OLIO is also design by watchmakers, uses 316L SS, and has a water resistance 50 times greater than that IPx7 with no time limit like IPx7 has.
As far as the band, you can get decent quality folded SS bands for around $15-20 USD at full retail price.
A bezeless square display can be done. It requires an approach not seen in smartwatches though that makes assembly a little more difficult but is still doable. Also, "Off the shelf" designs simply don't cut it as it requires the "crystal" be cut a certain way.
Have your guys look over "U.I Design", "Why this Martian.. ", and "I bet your smartwatch..." links in my signature below. Feel free to pick my brain and use the information in the links. The minimum I ask is that you give proper credit if you use any of it.
Looking at your G+ posts, nice job with the Ingenic BTW. I designed and built a smartwatch using the same platform. Too bad I killed it during a 5 ATM water resistance test.

Hi Lokifish, again useful details and feedback.
You are right, a nice and decent band is probably available on AliExpress for less than 20 bucks, but we made our with a different manufacturer and for the first batch we ended up with a cost of 28$.
This is another reason why we want to get this project into the community, to get feedback and suggestions from people that faced these problems before us.
About OLIO, of course they used high quality materials, a nice design, but I personally disagree about the ROM and UX choices (but this is my personal feeling). The point for me it's about the price. Pebble manufacturer their watch for 18$ and sell it for almost 199$, now dropped to 149$ if I am not wrong.
We are a startup and we will probably endup in some incubators or crowdfunding website in order to start the mass production. Probably the price will be around 199$ on retail but again, the prices and costs we are facing are a bit different than the one faced by watchmakers that have been on the market for many years.
What we believe is different between OXY and the rest of the world is the community, we want to make an open product, we want to make the customer capable to install custom ROM, customize the body and more. This is where we see the added value that other watch makers do not have at the moment.

@Lokifish Marz - thanks for the reply and pointing out OXY ... I feel like there's ... just a little hope ... maybe
@raffaeu - please take into account Lokifish Marz's advice, he will be very valuable to you, from a historical, current & future point of view. You'll save a lot of time and effort.
There are only a few people in the world that can make a decent, let alone a 'good smartwatch', due to greed/profit, but it can be done with the right goals and vision. Always know your history! Courtesy to the Martian ... again
I'm not a techy as such, but an important aspect of a good product is the non-functional business aspects, how to make a robust watch and then marketing, communication, support, together with making a little profit of course. Techies alone can't do this (no offense). Out of desperation we started the Nowt Watch thread, please have read, some very interesting discussion. No doubt you're at a stage where you can't go back with your current products, but we can always better our understanding and add to our knowledge and experiences.
I purchased an Omate clone recently (I had to get it out of my system), some of the non-techy issues, charging it - a pain! Straps - awful! A companion watch, should still be like a stand-alone watch first, meaning, above all its a robust time-piece that many can/would use without a phone as maybe a sports and leisure watch.
I'm curious, what does OXY mean? You have my support if you want it. I used to be a software tester, as well as marketing, strategy, process ... all that boring important stuff. Good luck

@Lokifish Marz has some interesting articles and idea that we are taking into consideration. Our primary targets are:
make an open source product
build a brand and trust from the community
make a real watch, solid, durable and with style
We designed OXY to being able to run with a phone and without, in fact without the battery stay charged for almost 1 week. Secondly is the charger which is magnetic, so that our customers are not having the frustration of the USB cable pain.
We are here to get feedback, idea and of course help. Anybody is welcome to join us, we are also hiring so anything is possible. Of course we are a startup so we still need to pay salaries and bills but we are not willing to become rich but we are willing to build a trusted brand for IoT products and more precisely for smartwatch. I always say that OXY is a mission for me and not a company.
OXY is an acronym for oxygen, something that you need and that's required to humans to live.
Feel free to contact me @simple1i and we can discuss further our project. In the meantime I'll have a look at your links.

Oh I see Oxy. I do like the name Horology, that's what all good (smart)watch lovers are, there's an idea for a name of a smartwatch.
Correct me if I'm wrong, but you decided to used Android because it's the cheaper/faster (way to get it up and ready) option? Do you have Playstore on the OXY? Google can be very awkward about this.
Listening to the tech' community is a good thing, but for a 'fine dining' watch the experts are few, you need the Horologists, the real trick to to know what opinions to take on and what to discard. Then its a matter of goods ideas/functions vs costs. This might be a tough one to address, but the OXY needs to be either better then the Moto 360 2's (rumoured specs) or similar with a lower cost. So far I'm impressed. I am waiting to see what Pebbles does with the I/O port on the back of their watch, what hardware add-ons will they come up with? A good future proof strategy for them to expand functionality.
I'll be in touch.

@simple1i it was not easy, we had to search for conflicts with other trademarks, copyright and we also needed something simple to pronounce considering that our product will be sold worldwide. OXY sound easy but it is still a nice sound to pronounce
Our PCB is an extension of Ingenic Newton2. We had to modify the plug for the display because the original one was not enough for round and square displays plus we added an heart rate, a vibration motor a different Bluetooth and a Lipo battery of 400mAh. We changed the USB port and overall we came up with the cheapest but more flexible solution.
Why? Because we have a public AOSP for Android 4.4 and Linux which means that our product can fit any development configuration without any license problems. Just use git, download our AOSP and create your own smartwatch.
Google play will be added later, as I said our goal is to provide an open platform with a default set of apps but without any license or warranty limit. Our license and warranty will cover only the hardware, about the software our customers will be able to fully customize the product.
For sure v1 won't be perfect, for sure we will need time to build up a community but based on the fact that we have an AOSP on git, that you can easily make custom apps with Android studio and that our price range will be lower than other android smartwatches, I think and hope that our product will be well known very soon.
Finally, we will run a crowdfunding but our mass production is already set. A big, big advantage compared to other crowdfunding campaigns

Unless Google has retroactively changed a number of things and not published it, official Google Services support (certification, service framework, Play Store, etc) is a no go. A couple of smartwatch manufacturers found out the hard way, one of which made it into tech news because of it. That's just one of many sites that covered it and I was working directly with Omate at the time this happened. The only smartwatches with official support run Wear, which requires partnership status.
Here's a good place to start

@Lokifish Marz partnership status is a no go. Also Pebble tried somehow to have a sort of partnership with Google, even if Pebble does not run Android at all, but they go a big no. Regarding Android WEAR, we have submitted in June 2 requests including draw, project details, hardware details and more and we never got an answer from anybody. We know that our OXY can run Android WEAR, we also took apart the SDK of Android WEAR to see how it works and at the end we choose to stay Open Source and give up on Google WEAR for now. Then in the future anything can happen, we are totally open to any conversation but our mission is to make an Open Source Smartwatch, so having a smartwatch locked down by Android WEAR .apk is not our business model right now. The giant Samsung has left Android WEAR and also OLIO did not even approach Google at all. Why? Probably because Google is taking some business decisions that cannot fit all watchmakers out there right now.
About Google Play, that's a different story. Our current hardware is better than Asus Zenwatch and the Moto 360 v1.0, the only limit for Google Play is the resolution. Our Round watch has a resolution of 400x400 while the squared has a resolution of 320x320 and we are using the same displays manufacturers used by LG and ASUS. But again, when you talk about smartwatch, you open a Pandora Box. It is the new business for any manufacturer, Forbes announced an estimation of over 30 billion dollars business between now and 2020.
But again, we can manually install Google Play and it just works fine, so what's the point here? We need first to create a community, distribute our product with a basic ROM so that users can receive notifications, phone calls, download and create watchfaces and all the things you want to achieve with a smartwatch. We have already setup an Azure play store where any developer can grab our SDK and our Genymotion virtual image, create apps and distribute them via our Cloud.
Then, probably next year, we will see how the things go and we will be able to present again a request to Google for both, Android WEAR and Google Play.
Again, I have spent now almost 1 year in R&D and I feel confident that Android WEAR is a closed business. You must be a big firm otherwise is a no go for now. About Google Play I am more positive but only time will say. For now we are focused on our website and marketing campaign, building a community and customizing our existing ROM and SDK. Btw, if you look at the potentialities of OXY, we have already a more powerful product in terms of frameworks and hardware, than a Pebble, which has sold more than 1,---,--- pieces between 2012 and 2015. We also got a conversation with Cyanogen which gave us a go to customize Cyanogen for OXY but at this point is worth to have our own Open Source Android version and move from there with the help of the community.

I get the issues with Wear and Google, I've been there multiple times. I also agree that open source is needed for the development community. The issue with not having Google Services support (Play Store) on an Android based smartwatch is that a fully stocked app store needs to be in place and filled with all big names like Facebook, EAT24 and the like and properly formatted to the display/UI/UX. If not, it severely limits your customer base. That's why many of the Chinese based smartwatches have had a hard time getting traction.
Now if you have a long haul plan that brings in average Joe smartwatch and watch buyer on, lets say, v.2 that's great. Keep in mind that after the multitude of less than stellar attempts by others, both xda and G+ can be very unforgiving. Especially if crowdfunding is involved.
This is starting to get into areas where private conversation may be justified so lets table this until after you make a decision. Then we can pick it up elsewhere.

@Lokifish Marz you got the point and probably you got it because you have been there before us. The only big difference thing is that we want to build a smartwatch, I don't think it would be of any use having a squeezed Facebook or Google+ app on your 400 pixels smartwatch. We are focusing on other criteria.
Motion track so that you don't have to press a button to view the time, real time notifications that when received turn on the display and show the notifications on top of the watch and many other watch oriented functionalities. V1 will give to crowdfunders a working "companion", a smartwatch that is a smartwatch, a companion app that can download .apk and install them and a decent SDK that allows developer to create custom apps and watchfaces or customize existing functionalities.
I am open to have a nice conversation with you guys. This month I'll visit China and Taiwan soon, where we are manufacturing the watches but it would be nice to setup a private call/chat for when I'll be back. Probably you know better than anybody else other members of XDA that may be seriously interested and involved in the project.

Update
We are preparing some VMs on Azure running Ubuntu LT12 with our Android AOSP source code.
Right now we have 3 versions for the AOSP: Android Square watch, Android Round watch, Ubuntu Touch.
Compilation is quite easy, for Android is something like:
./build/smk.sh --preset=oxy_v11_wisesquare_iwop
./build/smk.sh --preset=oxy_v11_naturalround_iwop
Next step for us is to host the whole repository over a public Git and distribute the Ubuntu VM so that anybody can start to download the VMs (already synchronized) and contribute. As soon as everything is ready I will open a different thread and start to have private conversations with the people interested in the OXY project.

Re: Ingenic Newton2 - (someone made this point) you can buy the Newton1 or Newton2 as a devkit, but you cannot buy the modules wholesale. So this isn't truly a SoM - it isn't meant to buy off the shelf and integrate into a product. It's meant to be a reference design that you can either copy, or tweak, or modify in to suit.
In other words, with Newton, you're still going to need to have someone manufacture and assemble PCBs, and it'll require a normal (and expensive, unpleasant) certification process. A true SoM would come pre-certified, making that process a lot easier (you still need to do a certification, but one one that's much less rigorous and costs a lot less)?

simple1i said:
Re: Ingenic Newton2 - (someone made this point) you can buy the Newton1 or Newton2 as a devkit, but you cannot buy the modules wholesale. So this isn't truly a SoM - it isn't meant to buy off the shelf and integrate into a product. It's meant to be a reference design that you can either copy, or tweak, or modify in to suit.
In other words, with Newton, you're still going to need to have someone manufacture and assemble PCBs, and it'll require a normal (and expensive, unpleasant) certification process. A true SoM would come pre-certified, making that process a lot easier (you still need to do a certification, but one one that's much less rigorous and costs a lot less)?
Click to expand...
Click to collapse
@simple1i You got the point. We bought Newton2 and made our watch using 3D print. Later we joined IWOP (Ingenic Watch Open Platform) which is a custom version of Android but more powerful than WEAR and better designed. At that point Ingenic gave us access to resources that are absolutely not available to private, so you can purchase the Newton2 dev kit but you cannot go far without their IWOP platform.
After that, we joined a partnership with two manufacturers, which are partners of Ingenic, and start to built our PCB and changed the Display (the display of Newton2 kit sucks, it has only 130 DPI).
About certifications, there are two phases. First you need to be sure that your PCB is ready for mass production, second, when the smartwatch is ready, you have to make IFC and CE at minimum, depending on where you want to sell. And this is the most painful part cause especially for CE, the process is long and full of obstacles. Consider that products like Pebble or other crowdfunded watches were shipped without any certification cause they were T2 prototypes expressly produced for the crowdfund campaign.

It looks like a nice piece of kit - in fact I love the design, it actually looks like a watch! Unfortunately, I'm not really sold on the idea of buying a 'smart' device where there's a very good chance of there being zero app development. Android Wear is rubbish right now (and of course, as you say, is a closed platform which creates big issues for us 'experimental' types and smaller organisations like yours trying to bring a device to market) but at least it's a group of companies working towards a common goal - in my mind that's far more likely to foster a community of developers than yet another smartwatch platform with a small userbase which will depend on yet another third party companion app and the headaches that creates with ongoing OS updates and trying to properly handle notifications and other interactions with the host device. I love the Pebble platform and larger ecosystem - I find the hardware and usage model vastly preferable to Wear (passively lit displays and buttons vs backlit displays and touchscreens, though I prefer the black and white ones, the Time lacks the contrast that makes the OG so easy to use AS A WATCH.) but they're odd looking devices which are 'obviously' not normal watches (not that I care, but I guess most people do) and the companion app has serious issues - they tend to get fixed fairly promptly but other app updates cause new issues pretty frequently - I still can't figure out how to stop it giving me notifications from the GMail app twice... What makes you think you could even do as well as a company who easily garners the kind of support they do on Kickstarter (and hence probably has a sizeable budget for a development team)?

Azurael said:
What makes you think you could even do as well as a company who easily garners the kind of support they do on Kickstarter (and hence probably has a sizeable budget for a development team)?
Click to expand...
Click to collapse
@Azurael you make a good point here.
I do not want to talk about WEAR because it's obvious that WEAR is the biggest market so far, but only because Google is pushing really hard to get tons of Watchfaces and Apps available for their platform. Also, comparing ourself to WEAR will sound very arrogant. We will never be able to become big like Google WEAR community and this is not the mission of OXY.
About Pebble, if you look at their backlog, most of the incoming releases have bug fixes and enhancements of the Firmware. And this is after almost 4 years (Pebble started in 2012). They sold their crowdfunding watch made of plastic, without heart rate, without AMOLED touch display and without microphone or speakers (1 version of pebble) for a range between 99$ and 149$. We will sell OXY for 199$ in PRE-SALE, and in my opinion that's a great deal compared to the hardware of the Pebble.
So, on our side we played the "partnership role" with Ingenic Semiconductor. Ingenic has developed an entire platform on top of Android AOSP called IWOP (Ingenic Wearable Open Platform). It is a set of APIs that allows you to achieve exactly the same results of WEAR but even more. It is designed specifically for Ingenic Hardware so it uses less energy, it is bug free because the hardware is tested and provided by Ingenic (so no issues with multiple smartwatches vendors) and it is already largely adopted in Asia. The advantage is that behind us there is a big hardware company which supplies already thousands of pieces to Chinese manufacturers, so it is in their interest to keep the platform up to date and bug free.
Of course we lack on apps, this is the only problem of OXY and I am totally aware of, but I am not worry about it. When Pebble came out, and same applies for WEAR, there were almost no apps or watchfaces available. After a couple of years of adoption the marketplace became bigger and bigger and now the two platforms are well known. Compared to Apple Watch, our SDK is way more powerful and more developer friendly.
We will play the same strategy here, except that we have already commissioned almost 100 apps to an external Software House in order to have a pre-set of free apps available on our platform as soon as we will be out with our PRE-SALE campaign. Than, we will start our "developer program" which will grant to each developer a free OXY smartwatch and access to all our documentation and articles. In addition to Pebble or WEAR with OXY you can also create your own ROM, your own Home Launcher and customize even the kernel. I am sure that many developers will be happy to put their hands on such a platform and get a smartwatch for free.
We have already discussed with Ingenic this topic and they are eager to expose their platform to the US/EU market, considering also that we will be the first company selling MIPS architecture in EU and US I feel confident that the gap about the lack of apps will be covered soon.
On the business plan, we will probably feed the platform for 2015/2016, so a low margin of profit will be generated but again this is not our plan (to generate money) but to make an open platform for smart devices. I think that it's important for us to explain exactly our mission in order to get the right amount of followers. Plus a bit of "viral marketing" would be beneficial too

Hardware talk
On the hardware side, could you have added more sensors if there was a need for them? And are any disadvantages for adding lots of extras sensors, like power consumption, over heating or less space to work on the PCB? Of course for every sensor you need an app for it.
Others might disagree with this view, that sensors make a device comes alive, the watch can sense more about its environment, just like a living thing. Also with the open source OS and SDK devs can make use of more of the sensors, making the watch a multi purpose device. I was hoping for a compass, it's one of those things that many won't use but like the idea of having it, just like a Swiss Army knife.
A barometer with a compass and heart rate monitor, could appeal to the sportsman. The Suunto watch gives nice weather icons to a good degree of accuracy. At least there enough sensors for the development of an app that can detect if the watch is being worn or not to stop certain functions like notifications and maybe even put the watch to sleep to save battery or have it on 'bedtime' mode.
Another advantage of having lots of sensors is that it makes the watch more of a stand-alone device.

If you talk about the Newton2 development kit the short answer is no, the long answer is yes, but with some re-design. We had to re-design the PCB of the Newton2 because we added an extra BlueTooth for iOS, an Heart rate sensor, a vibrating motor, a microphone and 5 speakers. Plus we re-designed the USB charge which is an extra PCB in the Newton2, while on our watch is into the same PCB.
Finally, the biggest and most complicated step is about the display. Newton2 use an MIPI interface specifically designed for their display, so in order to fit a Round and Square display from commercial companies like AMOLED Corp you have two options:
Make two PCB with two different MIPI, one per Display
Modify the displays MIPI to fit the same plug and play mechanism
We did not put a Baromoter because it is not easy to find a good provider and it does not deal well into mini PCB. About the GPS, we had one but we removed because it is absolutely battery drainer. If you run 3-4 hours with your GPS on the watch will end up without battery, while capturing the GPS from your Phone and streaming the amount of mt into the Watch app is way easier in terms of power consumption.
All weather apps that you see on Smartwatches are not using an internal barometer but they simply get weather conditions from a public HTTP API and stream the result into the Watch from your Phone.
What we have in additional is the WiFi so that you can run the watch in autonomous way, for example OXY can detect if you have internet on your watch, if don't then it grabs info from the internet of your Phone.
You can get fancy with sensors, we would to introduce in the future V2 more health sensors but it is early right now and you still have to deal with minimal space, each mm count.