I'm thinking some time about the possibilities to bring back some life to my loved Nokia 3310 by developing some software for it. The only downside is that there is not really much information on the Internet about the subject.
I've read that there is a SDK called Nokia PC Connectivity SDK 3.0, but every link that I tried is very old and the download links are always broken. Searching on Google just gives results to Mallware websites and the Nokia Developer website only holds an archived forum section without file support..
Does anyone knows where I can download this SDK or has a better idea/suggestion about developing software for this dinosaur of a phone?
AFAIK the offering is no longer available from the original site, thus I would not recommend using any versions available on any other site.
Anyway, the PC connectivity as far as I remember did not really enable you to develop any software for the device as such, it was used for making apps that could connect to the services of the device (such as SMS, logs etc.)
Quick internet search also suggest that the device might not even support AT commands, thus I would assume that there is no development offerings available for that old device anymore.
Related
I've seen this topic going around and the answers on each site and post have given it a wide range when talking about how to automate IOS devices from Windows PC.
One side, I've seen it where mainly the answer is: it's not possible due to Apple's rules, or its really messy to set up and not worth the effort to maintain, (though not explained in detail why its messy.) On the other side, I've read articles and posts about recommendations of IOS simulators such as iPadian, Smartface, etc; along with articles suggesting to stay from this software recommendations stating that they likely contain malware and viruses.
I've found other sources suggesting Experitest, Appium Studio, Quamotion, TestProject to test and automate IOS on Windows PC. However, after reading the concerns of being cautious around these sites, and unable to proof if these studios/software legitimately support simulating real IOS environments on Windows and the arguments that are against going this approach, I can't tell which sources are reliable on this topic anymore.
The interest for me asking this question, as you can guess, is that I want to find a way to automate IOS on Windows and experience how run tests on iPhone.
I usually write my code in Eclipse Studio and use Oracle VM to create Android Emulators to test on. I'm fine if I need to have a physical IOS device in order to test.
All advice is appreciated.
Thank you
The best option I would suggest to automate iOS app on Windows is to use cloud based solution like BrowserStack, SauceLabs, etc.
This way you're sure that you will be using actual iOS device and the app would behave the same way as it would on real physical iOS device.
You can even inspect the app using Appium inspector and run the tests with ease as well.
The only drawback of using such solution is that most of them don't support latest version of Appium.
So the work around for this would be to setup Microsoft Azure DevOps pipeline on Mac OSX virtual machine and use latest Appium server version.
The tools you mention - Experitest, Appium Studio, Quamotion,... all use the same approach: they communicate with real, physical iOS devices over a USB connection and then launch an agent (WebDriverAgent or similar) on the device which you can use to automate iOS devices.
They will usually require you to at least configure an iOS developer certificate and provisioning profile (much like you would when you are testing on a Mac).
Most of them also offer you a free trial and support, so you can go ahead and install the software and give it a try.
I apologize if this has been covered elsewhere. I have researched this topic to the best of my ability but I am still unsure of the answers I have found. I am a senior in college and I am developing an app to essentially act as a remote control for a device that my team is building for our senior capstone project. Everything is progressing fine for the Android app etc., but we are interested in developing an iOS app as well. We were steered toward Visual Studio 2015 or later for this since none of us own a Mac. We do not have an iPhone and we are not interested in trying to actually sell or deploy the app officially. All we really need is a means to simulate the iOS app on a PC and demonstrate that the functionality is still there to control our device.
I have seen several posts stating the requirement of a Mac regardless to, at the least, handle conversions for any app development on a Windows machine. I have also found a couple posts with a potential work around that involved installing a Mac VM, though I am not sure if these are "legal" solutions or not? We do not have it in our project budget to purchase any Mac systems, OS, or cloud services to develop the app. I have only done light work on Macs unrelated to programming so I know very little about what is possible regarding VMs etc.
At this point I am looking for some clarity on whether there is an actual legitimate and legal means to simulate an iOS app using Visual Studio and a Windows PC only? In our case, we would need the simulation to be able to connect to our device wirelessly and control it. It is OK that the physical device would actually be a Windows laptop, the CS department just wants to see that we have developed software that could in theory work on an iOS device. We would be presenting our work in detail during weekly updates so the solution would need to be above the table in all regards.
I apologize if this is answered elsewhere. The options in Visual Studio and most of the guides online are pretty unclear about what you can and can't do specifically under the various project types. We didn't want to get too deep into development with C# only to hit an impassable wall and lose all that time. It seems Apple keeps everything under close guard so I was suspicious about the VM alternatives to having a Mac. Thanks in advance for you time!
You must have a Mac to develop iOS apps, either to act as a build server, or as your primary development machine. Even when using Xamarin, the build tools and iOS Simulator are provided by Apple and will only run on Apple's OS. You can only legally run Mac OS on Apple hardware.
Just to add to the previous (and correct answer imo) which states that you need a mac to legally build IOS apps.
You don't need a powerful mac in order to do the building. I've been using a mac mini as a build server for a year now with no major problems. I wouldn't want to do any actual development on this machine, but it's great for sitting in the corner and doing builds sent via visual studio.
You can still do all IOS Dev on windows with visual studio (connected to the mac for building). Additionally with the enterprise version of VS you can run the IOS simulator on the PC, but again it requires a connected Mac. Although I'm hoping that they will eventually bring this functionality back to community users.
In your specific (academic) case whether or not you do manage to get a mac for building, I would suggest looking at Xamarin Test Cloud for providing evidence that your software will work on a large number of devices.
I have a native iOS application, I want to host it on my own server, and provide a link to download it. I am relatively new to this field and dont have much experience with hosting apps on server. So it would be great if somebody could help me with the steps.
Thanks
Why not just let Apple host it in the store?
Consider taking a look at distributing the app using OTA (Over the Air) assuming you have an Enterprise Apple Developer Account.
There's a guide here: http://aaronparecki.com/articles/2011/01/21/1/how-to-distribute-your-ios-apps-over-the-air
Or here: https://longtrieuquang.wordpress.com/2014/08/01/how-to-distribute-your-ios-app-ota-with-enterprise-account/
For various reasons, it is terribly bad practice to host iOS apps on your own. For starters, there is absolutely no quality or signature control. There is also no assurance for the user that what they are downloading is safe.
For this reason, Apple pretty well has it locked down that you HAVE to have your app in THEIR store, and nowhere else.
Even if you could provide the binary, good luck getting people to ever download and install it.
Android is very similar in this respect. I host my own apps from my own servers. But only for development purposes. Production is all handled by Google Play (and Amazon). I never expect anyone will actually download the local version. And I don't blame them.
I want to play with screen sharing between my apple devices. I know WiFi direct is part of what supports the Airdrop feature to send files between macs and want to play around with that API.
I'll keep on searching, but was wondering if anyone has done this before or if Apple won't let you touch that API.
I'd also be happy to hear about any libraries that may be available specifically for raspberry-pi or for Linux in general.
Thanks
A friend of mine demoed an Android project he was working on the other day that utilized the AllJoyn library. AllJoyn is an open source API that supports Wifi-direct as well as other wireless protocols and is supported on Android, Linux, and iOS. It might be worth looking in to.
https://www.alljoyn.org/
We have a fairly simple mobile application, completed for iPhone and Android that does the following:
queries a web service to verify the user's account information
display an animation to show that the user, in fact, has a valid account
We got the application working very quickly on a PlayBook by using the Android version.
Now the customer has asked us to explore getting it to work on other BlackBerry devices.
None of us know that much about BlackBerry, and the main source for our question returned from google searches (http://us.blackberry.com/developers/choosingtargetos.jsp) comes up as 404 page.
According to this chart there is still a wide variety of devices in use. Which ones does it make sense to target?
Thanks
I had posted an answer last year about this here on stackoverflow, but as you noted, that link has recently broken.
The only thing I've found that's similar is this BlackBerry developer page. It shows, for example, that paid apps are being purchased by devices that are about 97% on OS 5.0 and above.
From what you've told me, I don't know that your app is going to be that different on different devices, aside from maybe the obvious smartphone vs. Playbook difference. Different devices certainly have different screen sizes, so you'll need to make sure your UI is coded to handle that gracefully.
If you guys are new to BlackBerry, you might want to stay away from OS < 5.0. There are some things in prior OS versions (e.g. location services / maps, browser, and networking) that are a little tough to work with, and with such a small percentage of paying customers still on OS < 5.0, it probably isn't worth it to you.
So, I guess I'm recommending that you target specific OS levels (e.g. 5.0+). That will be a bigger driver for how you build your app, than a specific set of devices. This is because each OS version adds more and better APIs to use.
Once you've decided which OS to target, then you should download the SDK for each major OS. For example, if you use the Eclipse BlackBerry plug-in, you can install the 5.0 SDK (aka component pack), the 6.0 SDK, the 7.0 and 7.1 SDK.
Once you have those SDKs installed, you'll then have a bunch of simulators (each SDK has a simulator folder). Run your app on all those simulators, and that'll probably be a good start.
Of course, there's no substitute for running on real hardware, too, but if your app does mostly standard things (not interacting with hardware sensors, just displaying web pages, and making HTTP requests), the simulators should give you a pretty good test environment. They certainly will give you all the screen size configurations.