21–30 of 38 posts
Keep up the good work, passion and initiative like this will take you far.
It looks cool! Well done! :) As others have commented, in my opinion Windows Phone will have a negligible influence on the mobile market going forward. I think it would be a much better investment of your time to start developing on either iOS/Android (or both!) as early as possible. Good luck!
The future of Windows Phone is solely dependent on how Microsoft executes its universal app strategy. If they successfully launch a way of running the same app on Windows (desktop/laptop), Phone and Tablet (non-x86) then it may be able to come back from the dead. Unfortunately Microsoft have almost no experience at doing such a thing, they have always lived in their [big] Windows eco-system bubble and that may very w…
It's a matter of time before people realize they can use Xamarin to port a Windows app to iOS/Android in a matter of days.
I am quite ignorant when it comes to Windows Phone development, mainly because it never took off how Microsoft wanted it too. Would you mind sharing the tools and technologies used to develop your app? If not here then a blog post would be fantastic, describing the process from start to end, issues you had with the tools/processes, etc. One small bit of feedback on the UI, make the background for the "Type or tap des…
Professional Windows Phone developer here. Here are the tools/processes usually used in WP8 app development: IDE: Visual Studio Language: C# or F# UI: XAML (WPF) and Visual Designer Deployment: Windows Phone simulator (really good) or Device Architecture: MVVM (Model-View-ViewModel) with Two-Binding If you do it right, you should be able to reuse 80-90% of the code in a Windows 8 app. With Xamarin, you can reuse 50-7…
I am quite ignorant when it comes to Windows Phone development, mainly because it never took off how Microsoft wanted it too. Would you mind sharing the tools and technologies used to develop your app? If not here then a blog post would be fantastic, describing the process from start to end, issues you had with the tools/processes, etc. One small bit of feedback on the UI, make the background for the "Type or tap des…
I am quite ignorant when it comes to Windows Phone development, mainly because it never took off how Microsoft wanted it too. Would you mind sharing the tools and technologies used to develop your app? If not here then a blog post would be fantastic, describing the process from start to end, issues you had with the tools/processes, etc. One small bit of feedback on the UI, make the background for the "Type or tap des…
Professional Windows Phone developer here. Here are the tools/processes usually used in WP8 app development: IDE: Visual Studio Language: C# or F# UI: XAML (WPF) and Visual Designer Deployment: Windows Phone simulator (really good) or Device Architecture: MVVM (Model-View-ViewModel) with Two-Binding If you do it right, you should be able to reuse 80-90% of the code in a Windows 8 app. With Xamarin, you can reuse 50-7…
Definitely got a lot of feedback from my friends to get it on iOS and Android. Haha, and yeah, Android Studio is quite the hassle compared to Visual Studio, but will definitely get through it :)
Don't worry too much about what platform you initially develop your app for -- if you can validate your concept then it shouldn't be hard to find assistance porting it to other platforms. Too many people get tied up on "what platform should I develop for?" when they could be spending that time getting an MVP up on _something_, validating it and getting the ball moving.
I just happen to own a Windows Phone, and commuted a lot, while in the process, missed quite a few stops due to tiredness and overall school stress.
Don't worry too much about what platform you initially develop your app for -- if you can validate your concept then it shouldn't be hard to find assistance porting it to other platforms. Too many people get tied up on "what platform should I develop for?" when they could be spending that time getting an MVP up on _something_, validating it and getting the ball moving.
I believe he made the right decision in starting with Windows Phone. Not only is it easier to build an app on this platform, but once he validate the idea, he can easily port the app to iOS and Android with Xamarin and share at least 50% of his code with all platforms. The opposite (porting an iOS/Android app to Windows Phone) is much less trivial.
It looks cool! Well done! :) As others have commented, in my opinion Windows Phone will have a negligible influence on the mobile market going forward. I think it would be a much better investment of your time to start developing on either iOS/Android (or both!) as early as possible. Good luck!
Already starting on Android devices :)
It looks cool! Well done! :) As others have commented, in my opinion Windows Phone will have a negligible influence on the mobile market going forward. I think it would be a much better investment of your time to start developing on either iOS/Android (or both!) as early as possible. Good luck!
Already starting on Android devices :)