DOCSLIB.ORG

Mobile App Development

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mobile App Development Mobile app development Tiberiu Vilcu Prepared for EECS 411 Sugih Jamin 2 January 2018 https://education.github.com/pack 1 2 Outline Not the same as before 1. Mobile app programming and MVC Developing and coding mobile apps is not like programming you’ve 2. App lifecycles done for other classes. 3. UI and UX It is largely event-driven and does rely only on serial code execution. 4. Working with iOS It’s an opportunity to integrate and apply concepts from other CSE 5. Working with Android courses taken. 6. Working with web apps 7. Third-party frameworks 8. Resources 3 4 Event-driven programming MVC 1. Define a UI with interactive elements Software architecture pattern to split application in 3 parts. 2. Add event handlers to UI elements Model: contains app behavior, data, logic, and rules 3. Add handlers for internal state changes View: contains any output of information (visual or audio) 4. Process and store data locally and externally, use APIs Controller: contains inputs elements and connects the model to the view through interaction 5. Test extensively 5 6 MVC example Abstract app lifecycle Xcode and Android Studio Interface Builders are good examples. Not running: not launched or terminated by system Model: XML code that represents your UI Inactive: in foreground, running code, not receiving events View: graphic representation of your UI in the editor Active: in foreground, running code, receiving events Controller: draggable and modifiable elements and properties Background: not in foreground, running code, before suspension Suspended: not in foreground, not running code, still in memory 7 8 iOS app lifecycle iOS UIViewController lifecycle • applicationDidBecomeActive(): app is about to become the foreground • viewDidLoad(): called when controller is created app • viewDidLayoutSubviews(): called whenever a subview needs to layout • applicationWillResignActive(): app is no longer the foreground app • viewWillAppear(): called when view is about to show, used to customize view settings • applicationDidEnterBackground(): app is running in the background • viewDidAppear(): called after the view shows • applicationWillEnterForeground(): app is moving from background to foreground • viewWillDisappear(): called before the view is removed • applicationWillTerminate(): app is being terminated • viewDidDisappear(): called after the view is in a disappeared state 9 10 Android app activity lifecycle User interface and user experience • onCreate(): activity first loads up To a user, UI/UX is the most important first impression. • onStart(): activity becomes visible to the user Their perception is strongly influenced by your UI. • onResume(): activity comes to foreground and user interacts Think of your code in terms of actions taken by the user (and the OS)! • onPause(): user is leaving activity (but not destroying) • onStop(): activity is no longer visible to user • onDestroy(): activity being destroyed by user or system 11 12 Tips when building UIs Things to know for iOS • Start simple: minimal views, minimal elements, minimal colors • You can only develop in Xcode on macOS • Plan your views/pages ahead of time • Apple Developer Account costs $99 (yearly) • Use a UI builder before doing it in the actual app (later lecture) • You should work primarily/only in Swift • Don’t hide important content or interactive elements • You can and should simulate on all various screen sizes • Follow Apple’s Human Interface Guidelines or Android User Interface • Certain features are only on newer version of iOS if you need them Guidelines • TestFlight can be used for beta testing (even A/B) 13 14 Tips before you begin on iOS Development resources • You can learn Swift as you go CocoaPods: dependency manager for Swift and Objective-C; automatically creates Xcode workspace • You will find bugs in Xcode; save/commit often and google problems Carthage: dependency manager for binary frameworks; does not • Xcode can automatically convert old Swift code into new code automatically modify project/build settings (however it's not guaranteed to work or be correct) Third-party SDKs: use of most public APIs require custom SDKs; these • Plan out data caching and storage ahead of time can be downloaded and build via the dependency managers • Don’t waste too much time on an app icon 15 16 Apple Developer account Publishing an iOS app You will eventually need an account for the class. 1. Create Apple Developer account 2. Login to iTunes Connect and create an “app record” • $99 for a one-year subscription 3. Create an archive in Xcode and run validation tests • Required to publish to App Store 4. Upload in Xcode to iTunes Connect • Gives access to betas 5. Choose a build, add app information, and submit for review on iTunes Connect • Gives ability to run/save your app on actual phones Be wary of content restrictions on the app store. Consider splitting accounts with other teams to save costs. Reviews usually take a few days. 17 18 Warnings about iOS / Swift Things to know for Android • Things change quickly in Swift! (currently 4.0) • You can develop in Android Studio on any OS • A lot of code online is outdated • Google Play Developer Console costs $25 (one-time) • SDK’s online also often outdated or use Objective-C • You will primarily use Java and XML You may need to build them yourselves • You should test on different phone emulators • Your entire team should be on the same versions of Xcode/macOS/ iOS 19 20 Tips before you begin on Android Publishing an Android app • Learn how to use Java and XML as you go 1. Sign up for a Developer Console with your Google account • Plan your activities and how they interact ahead of time 2. Build and sign a release version in Android Studio • Name your widgets and variables carefully; refactoring can cause 3. Create an application on the Console and update the store listing, problems content rating, and distribution • Don’t waste too much time on icons 4. Upload your APK and publish 21 22 Warnings about Android Mobile “web” apps • Android compatibility is very fragile Mobile apps written in a modern web framework. • Different API versions have widely different use percentages Can be written using: • Code may sometimes be underlined in Android Studio while correct • HTML as it takes time to refactor • CSS • Build often to view errors • JavaScript (React especially) Doesn’t require knowing gritty details of web-dev or mobile app dev. 23 24 React Native React Native pros Open-sourced software to build mobile apps from (mostly) JavaScript • Quicker development of two applications in parallel • Works in JavaScript and allows UI components to be added • Hot reloading can save a lot of time vs. compiling • Allows use of native (Swift/Java) code when necessary • JavaScript may be more familiar • Can reload a preview of the app without recompiling • Easily supports A/B testing • Compiles to iOS and Android applications through Xcode and Android Studio • Supported by big companies 25 26 React Native cons Apache Cordova • Inconsistencies between UI elements natively supported Open-source software to build unified web and mobile apps. • Not as polished or documented as original IDEs • Works with HTML, CSS, and JavaScript • Some unsupported features are hard to add in both versions • Wraps app into native container app used on mobile devices • Can cause major slowdowns in development • Supports native OS features in unified JavaScript API • Publishing apps is not the same 27 28 Ionic Ionic pros Open-source software to build unified web and mobile apps. • Quicker development of two+ applications in parallel Built on top of Apache Cordova. • JavaScript, HTML, and CSS for those familiar • Supports native OS features in unified JavaScript API • (More) native plugins that interact with OS • Includes front-end components that makes it look more like native app • Live reloading, A/B testing, and custom style/icons • More performance optimized • Large online community • Pro features for enhanced development 29 30 Ionic cons Picking an OS • There are limitations to features supported on the OS 1. Do a majority of teammates have access to a Mac? • Does not match the native look of iOS/Android apps 2. Is there an OS-specific feature to take advantage of? • Still creates hybrid, not fully native, apps 3. Is it a gaming app built through another platform? • Can cause major slowdowns in development 4. Is there a demographics difference between users? • Publishing apps is not the same 31 32 Picking a platform React Native vs Ionic 1. Is there a specific hardware feature not supported by web apps? • Builds a native app in Swift/Java • Defines UI by HTML/CSS, not JS 2. Will there be a complicated UI with many custom points of • In theory is “faster” • Has licensed style and icons interaction? • Has a more native OS-specific • Has good API documentation 3. Will third-party SDKs be used? look, important for users and community resources 4. Will front-end lag be an issue? • Is used by big companies 5. Is there experience with Swift/Java? 33 34 Previous lectures iOS Resources • iOS sample project repo: https://github.com/UM-EECS-441/ios-project-sample-f17 • Swift guide: https://developer.apple.com/library/content/documentation/Swift/Conceptual/ Swift_Programming_Language/index.html#//apple_ref/doc/uid/TP40014097-CH3-ID0 • Android sample project repo: https://github.com/UM-EECS-441/android-project-sample-f17 • Apple Human Interface guidelines: https://developer.apple.com/ios/human-interface-guidelines/overview/ • iOS development lecture slides: http://web.eecs.umich.edu/~sugih/courses/eecs441/f17/03-iOSDevelopment.pdf
Load more

Recommended publications
  • Practicalizing Delay-Tolerant Mobile Apps with Cedos
    Practicalizing Delay-Tolerant Mobile Apps with Cedos YoungGyoun Moon, Donghwi Kim, Younghwan Go, Yeongjin Kim, Yung Yi, Song Chong, and KyoungSoo Park Department of Electrical Engineering, KAIST Daejeon, Republic of Korea {ygmoon, dhkim, yhwan}@ndsl.kaist.edu, [email protected], {yiyung, songchong}@kaist.edu, [email protected] ABSTRACT 1. INTRODUCTION Delay-tolerant Wi-Fi offloading is known to improve overall mo- Wi-Fi has become the most popular secondary network interface bile network bandwidth at low delay and low cost. Yet, in reality, for high-speed mobile Internet access on mobile devices. Many we rarely find mobile apps that fully support opportunistic Wi-Fi mobile apps support the “Wi-Fi only” mode that allows the users to access. This is mainly because it is still challenging to develop shun expensive cellular communication while enjoying high band- delay-tolerant mobile apps due to the complexity of handling net- width and low delay. In addition, cellular ISPs are actively de- work disruptions and delays. ploying Wi-Fi access points (APs) to further increase the mobile In this work, we present Cedos, a practical delay-tolerant mobile Internet access coverage [1, 2, 3]. network access architecture in which one can easily build a mo- However, current Wi-Fi usage is often statically bound to the lo- bile app. Cedos consists of three components. First, it provides a cation of mobile devices. While this “on-the-spot” Wi-Fi offloading familiar socket API whose semantics conforms to TCP while the is still effective, recent studies suggest that one can further extend underlying protocol, D2TP, transparently handles network disrup- the benefit of Wi-Fi access if we allow delay tolerance between net- tions and delays in mobility.
    [Show full text]
  • Taxonomy of Cross-Platform Mobile Applications Development Approaches
    Ain Shams Engineering Journal (2015) xxx, xxx–xxx Ain Shams University Ain Shams Engineering Journal www.elsevier.com/locate/asej www.sciencedirect.com ELECTRICAL ENGINEERING Taxonomy of Cross-Platform Mobile Applications Development Approaches Wafaa S. El-Kassas *, Bassem A. Abdullah, Ahmed H. Yousef, Ayman M. Wahba Department of Computer and Systems Engineering, Faculty of Engineering, Ain Shams University, Egypt Received 13 September 2014; revised 30 May 2015; accepted 3 August 2015 KEYWORDS Abstract The developers use the cross-platform mobile development solutions to develop the Cross-platform mobile mobile application once and run it on many platforms. Many of these cross-platform solutions development; are still under research and development. Also, these solutions are based on different approaches Interpretation approach; such as Cross-Compilation approach, Virtual Machine approach, and Web-Based approach. There Cloud computing; are many survey papers about the cross-platform mobile development solutions but they do not Compilation approach; include the most recent approaches, including Component-Based approach, Cloud-Based Component-Based approach, and Merged approach. The main aim of this paper is helping the researchers to know approach; the most recent approaches and the open research issues. This paper surveys the existing cross- Model-Driven Engineering platform mobile development approaches and attempts to provide a global view: it thoroughly introduces a comprehensive categorization to the cross-platform approaches, defines the pros and cons of each approach, explains sample solutions per approach, compares the cross-platform mobile development solutions, and ends with the open research areas. Ó 2015 Faculty of Engineering, Ain Shams University. Production and hosting by Elsevier B.V.
    [Show full text]
  • Critical Capabilities for Successful Mobile App Development
    7 Critical Capabilities Your Mobile App Development and Deployment Platform Must Include Speed Mobile App Development and Ensure Wide User Adoption Executive Summary In today's mobile business environment companies are scrambling to quickly mobilize hundreds of B2B and B2E business processes or legacy applications. There are three main approaches developers can use to build mobile business apps: - Responsive web apps - Native app development - "Native quality" hybrid apps This whitepaper explains important differences between these three approaches, outlines 7 mobile capabilities that real-world business apps require today, and identifies the most productive development approach for getting these mobile business apps to market FAST. 1 | P a g e High Demand for Mobile Apps For competitive and productivity reasons, businesses and organizations are embracing mobile more than ever. Gartner forecasts enterprise application software spending to double from $300B in 2013 to over $575B by the end of 2018.1 Yet, Gartner also predicts demand for enterprise mobile apps will outstrip available development capacity by five to one.2 Forrester warns: “The CIO who fails in mobile will lose his job.”3 As a result, companies are trying to find new ways to enable their employees to develop business apps. Everyone from young IT or business workers with basic HTML5 skills, to IT developers with limited mobile experience and business analysts are exploring how to build apps to get routine things mobilized faster. Rising End-User Expectations Complicating the problem is the rising expectations of an increasingly mobile workforce. Employees are adopting mobile devices exponentially and demanding more business apps to do their work.
    [Show full text]
  • Factors Influencing Quality of Mobile Apps: Role of Mobile App Development Life Cycle
    International Journal of Software Engineering & Applications (IJSEA), Vol.5, No.5, September 2014 FACTORS INFLUENCING QUALITY OF MOBILE APPS : R OLE OF MOBILE APP DEVELOPMENT LIFE CYCLE Venkata N Inukollu 1, Divya D Keshamoni 2 , Taeghyun Kang 3 and Manikanta Inukollu 4 1Department of Computer Science Engineering, Texas Tech University, USA 2 Rawls College of Business, Texas Tech University, USA 3 Department of Computer Science Engineering, Wake forest university, USA 4Department of Computer Science, Bhaskar Engineering College, India ABSTRACT In this paper, The mobile application field has been receiving astronomical attention from the past few years due to the growing number of mobile app downloads and withal due to the revenues being engendered .With the surge in the number of apps, the number of lamentable apps/failing apps has withal been growing.Interesting mobile app statistics are included in this paper which might avail the developers understand the concerns and merits of mobile apps.The authors have made an effort to integrate all the crucial factors that cause apps to fail which include negligence by the developers, technical issues, inadequate marketing efforts, and high prospects of the users/consumers.The paper provides suggestions to eschew failure of apps. As per the various surveys, the number of lamentable/failing apps is growing enormously, primarily because mobile app developers are not adopting a standard development life cycle for the development of apps. In this paper, we have developed a mobile application with the aid of traditional software development life cycle phases (Requirements, Design, Develop, Test, and, Maintenance) and we have used UML, M-UML, and mobile application development technologies.
    [Show full text]
  • Browser App Approach: Can It Be an Answer to the Challenges in Cross-Platform App Development?
    Volume 16, 2017 BROWSER APP APPROACH: CAN IT BE AN ANSWER TO THE CHALLENGES IN CROSS-PLATFORM APP DEVELOPMENT? Minh Huynh* Southeastern Louisiana University, [email protected] Hammond, LA USA Prashant Ghimire Southeastern Louisiana University, [email protected] Hammond, LA USA *Corresponding Author ABSTRACT Aim/Purpose As smartphones proliferate, many different platforms begin to emerge. The challenge to developers as well as IS educators and students is how to learn the skills to design and develop apps to run on cross-platforms. Background For developers, the purpose of this paper is to describe an alternative to the complex native app development. For IS educators and students, the paper pro- vides a feasible way to learn and develop fully functional mobile apps without technical burdens. Methodology The methods used in the development of browser-based apps is prototyping. Our proposed approach is browser-based, supports cross-platforms, uses open- source standards, and takes advantage of “write-once-and-run-anywhere” (WORA) concept. Contribution The paper illustrates the application of the browser-based approach to create a series of browser apps without high learning curve. Findings The results show the potentials for using browser app approach to teach as well as to create new apps. Recommendations Our proposed browser app development approach and example would be use- for Practitioners ful to mobile app developers/IS educators and non-technical students because the source code as well as documentations in this project are available for down- loading. Future Research For further work, we discuss the use of hybrid development framework to en- hance browser apps.
    [Show full text]
  • Iphone App Development Checklist
    Iphone App Development Checklist Arturo often dredged evilly when thrilled Rodrique treadled humanly and argued her euphausiid. Municipal Thom puddles exceedingly and ungracefully, she battledore her econometrician horsing malevolently. Unmatriculated and unapproached Homer humanizing while annoying Otto stem her mozzarella duskily and parch beside. Advanced iOS Application Testing Checklist HTML Pro. A front-end checklist items are created for the purpose of going list a web application. Teaching App Development with another Course materials for instructors teaching Swift Engage students with your project-based curriculum and guide. Connect for developers are all the traffic and navigation elements of restaurant and unauthorized access to the requirements of effort in all the development checklist? This tool ask for parents and teachers to enterprise in developing a student's IEP The checklist includes items required by special education regulations. What please be checked before publishing an app to App Store. Top Mobile App Development Company Crownstack. As one shade the best iOS app developers we're well aware of defeat the adultery of iOS can equity and remember you're surgery to build an app for the Apple community you. When you enlist an expert iPhone application development company down have only know think he is equipped for letter a limitless scope of applications that. Will your app be integrated with device's features 14 Will to need cloud based infrastructure the shelter I have mentioned Android and iOS. Mobile App Testing Checklist for releasing apps BrowserStack. Checklist to a successful mobile app development Inapps. Even fill the development of the app starts the testers are handed over screen.
    [Show full text]
  • Edetailing With
    Sustainable Business Relationship Building Through Digital Strategy Solutions Development of Mobile Applications Overview . Introduction . History of Mobile Applications . Current State of Mobile Applications . The Future of Mobile Applications . Development Introduction • A mobile application (or mobile app) is a software application designed to run on smart phones, tablet computers and other mobile devices. History of Mobile Application The history of the mobile app begins, obviously, with the history of the mobile device. The first mobile phones had microchips that required basic software to send and receive voice calls. But, since then, things have gotten a lot more complicated. NX3 Mobile Application Development Services Native And Non-Native Frameworks Native Application Environment: . Android . iOS . Windows Phone 8 . BlackBerry 10 Non-Native Application Environment: . Phone Gap . Titanium Mobile Android . Based on the Linux kernel, Android started life as a proposed advanced operating system for digital cameras until the company realized that the market was limited compared to that for mobile phones. The Open Handset Alliance unveiled the Android operating system in 2007, nearly two years after Google’s acquisition of Android. The launch of Google’s foray into the mobile world was delayed by the launch of the iPhone, which radically changed consumers’ expectations of what a smartphone should do. IOS . Apple’s iPhone set the standard for the new generation of smartphones when it was first released in June 2007 with its touchscreen and direct manipulation interface. There was no native SDK until February of 2008 (Apple initially planned to provide no support for third-party apps). The iOS lineage started with Next STEP, an object-oriented multitasking OS from the late eighties developed by NeXT Computer (acquired by Apple in 1996).
    [Show full text]
  • Three Approaches to Mobile App Development
    APPROACHING MOBILE Understanding the Three Ways to Build Mobile Apps WHY ARE THERE DIFFERENT APPROACHES? Mobile software development is still software development. If twenty years of “desktop” software development taught the industry anything, it is that every application is unique. Every application has requirements that drive the decisions about how A responsible software Mobile app development is complex. it should be built. Some apps require maximum development strategy is built To build apps that reach all users, developers must access to hardware for rich visual presentation. deal with many different operating systems, SDKs, Some apps require maximum flexibility and the around a mixture of approaches ability to quickly deploy changes in response to development tools, screen sizes and form factors, that allow a business to cover as well as a technology landscape that is still in a business needs. constant state of flux. And if that were not enough, all software requirements while there are also several different ways to build mobile A responsible software development strategy is optimizing the time and cost of apps that development teams must sort through built around a mixture of approaches that allow a delivering an app." before beginning any new mobile effort. business to cover all software requirements while optimizing the time and cost of delivering an app. Choosing how to build a mobile app, though, can Forrester Research shares the same belief in its have the most dramatic effect on the eventual study, Putting a Price to Your Mobile Strategy, cost, time, and success of a mobile project. This suggesting developers not “get taken in by the is second only to determining the scope and allure of technology trends du jour.” The pattern for functionality of the app itself.
    [Show full text]
  • Mendix for Mobile App Development White Paper Table of Contents
    MENDIX FOR MOBILE APP DEVELOPMENT WHITE PAPER TABLE OF CONTENTS Market Demand for Enterprise Mobile 3 Mobile App Development Approaches 4 Native Apps 4 Mobile Web Apps 4 Hybrid Apps 5 Mendix Vision for Mobile App Development 6 JavaScript Pervasive as Base Technology 6 Hybrid is the New Native 7 Mendix Hybrid App Development 8 Create Powerful Mobile Enterprise Apps Without Code 8 Responsive UIs 9 Native Device Functions 10 Instant Testing 11 Publish to App Stores 12 End-to-End Mobile App Dev Flow 13 Open Platform For Any Mobile App Technology 14 The Platform To Mobilize The Enterprise 14 Conclusion 16 Mendix for Mobile App Development 2 Market Demand for Enterprise Mobile With the explosive increase in example, customer complaints issued smartphone and tablet use, along with through a mobile app may be part of the massive consumer adoption of a larger customer service application innovative apps and services, we are whereby the customer service staff in the midst of a mobile revolution. And view the complaints through desktop this revolution is fueling fundamental computers. In this instance, staff changes to application architecture. members benefit from greater context This is similar to, and probably even by leveraging multiple data sources that more impactful than, the earlier shift all converge and produce a 360-degree from monolithic systems to client/server view of the customer. architectures. A recent survey from DZone of more Modern applications require multi- than 1,000 global IT professionals channel clients and a scalable revealed that the biggest pain points for infrastructure. Moreover, they need to mobile app development are centered be easily deployed and rapidly changed around multi-platform development and based on user feedback.
    [Show full text]
  • Mobile App Development SEQUENCING & COURSE PLAN
    Mobile App Development Minor requirements Core requirements (6 units): ITP-115 “Programming in Python” (2 units) Design and program innovative and standards-compliant applications for Android and iOS ITP-265 “Object-Oriented Programming” (4 units) smartphones and tablets. Learn how to design mobile interfaces, use libraries to build apps that have [prerequisite: ITP-115 or ITP-165] the proper look and feel, and handle user input. Complete one of the following (4 units): ITP-341 “Android App Development” (4 units) [prerequisite: ITP-265 or CSCI-103] units required for units required for ITP-342 “iOS App Development” (4 units) minor: specialization: minor code: department: [prerequisite: ITP-265 or CSCI-103] Electives (8 units): 18 10 MOAP ITP ITP-303 “Full-Stack Web Development” (4 units) [prerequisite: ITP-265 or CSCI-103] ITP-310 “Design for User Experience” (4 units) ITP-341 “Android App Development” (4 units) Skills Careers ITP-342 “iOS App Development” (4 units) ITP-344 “Advanced iOS App Development” (4 units) » Android development » Mobile Developer [prerequisite: ITP-342] » iOS development » UX Designer ITP-345 “Advanced Android App Development” » UI design » Interaction Designer (4 units) [prerequisite: ITP-341] ITP-382 “Mobile Game Development” (4 units) » Mobile app ideation [prerequisite: ITP-265 or CSCI-103] ITP-442 “Mobile App Project” (4 units) [prerequisite: ITP-341 or ITP-342] Specialization requirements Policies Core requirements (6 units): » All minors at USC need 16 units that only meet minor requirements and do not meet any other major, ITP-115 “Programming in Python” (2 units) minor, or GE requirement. ITP-265 “Object-Oriented Programming” (4 units) » All courses completed for your minor or specialization must be completed for a letter grade.
    [Show full text]
  • Mobile App Device
    Request for Technology Fee Funds NOTE: A separate request should be made for each initiative. I. Department Number/Department Name: 360 College of Computing Title of Request (please be brief): Mobile Device Programming Equipment & Staffing Amount of Request (formula from detailed budget below): $120,428 Are there any installation/renovation costs associated with this request? Yes No If "Yes" then indicate the source of approved funding: (Note: Tech Fees are not allowed for installation/renovation) Executive Summary of Request (100 words or less): New resources and student assistant help are required to continue innovation in courses and student projects that are engaged in mobile device programming, primarily through the interdisciplinary App Lab and the iOS Learning Lab. Specific class and/or lab initiative(s) if applicable: Mobile App CS4261/8803-MAS, CS4803, CS100 Contact person for this request (incl. phone #): Clark (5-4706), Stallworth (5-3318), Ramachandran Indicate priority per department if applicable: Number of Indicate priority per college or unit: Number 5 of 13 II. Impact on Students - Provide course title, course number, and anticipated enrollments: Titles/Numbers of Course(s) All CoC students have access to these resources Anticipated Enrollments Graduate: 622 Undergraduate: 1,097 Total: 1,719 NOTE: Other impacts on students should be described in narrative. III. Narrative - Provide narrative justification for your intended use of the technology fee funds. Include narrative on how the education or research of the students will be enhanced. Also include how the request aligns with the Strategic Plan of Georgia Tech. Continue in the block below if necessary. Mobile devices are now ubiquitous in modern society and software development fuels much of the innovation cycle.
    [Show full text]
  • Student Activities of the Computer Science and Engineering Department
    Student Activities of the Computer Science and Engineering Department Sl_No Events Student Name Organizer Awarded Date South India Level Sanjay N S PESCE, Mandya II Runner Up 29-Feb-2020 Hackathon Event Soumik V 1 HACKMANIA 3.0 Nived B Sammith B S TCS Tech Bytes Quiz Sanjay N.S JSS University, Grabbed 6th FEB 27th 2020 2 regional Competition Sunad.K Mysore place National Level Event Sanjay N S PESCE, Mandya II Runner Up 25th & 26th HACKMANIA 2.0 Soumik V OCT 2019. 3 (Hackathon) Nived B Sammith B S Innovative Technical Govindaraju Y PESCE, Mandya Won First 14-June-2019 Project Exhibition-19 prize 4 The Project entitled “Controlling Energy Meter Using IOT”. Innovative Technical Gowda Tejas, PESCE, Mandya Won First 14-June-2019 Project Exhibition-19 Harish M, prize 5 The Project entitled Mohammed “Smart Blind Stick Ismail Khan S, Using IOT”. Prasanna Intra Department Amogh Babu K.A PESCE, Mandya Participated 11th May 6 Project Exhibition-19 (4PS15CS008) 2019 The Project entitled S.Kaushik NIE, Mysore Session Best 16th & 17th “Virtual Classroom Arkalgud, Y R Paper award in May 2019 using Augmented Vasuki Varuna, National 7 Reality (AR) and Sinchana. M. Conference Virtual Reality (VR)” Hadli , H N Shreyas “SPARK” A State Level Deeksha.M S PESCE, Mandya Participated 30th & 31st 7 Socio-Entrepreneurial (4PS17CS020) March 2019 Fest Presenting a paper on Sammith B S PESCE, Mandya Secured 27th March “Accident Detection and (4PS16CS093) Second Place 2019 Notification System are 8 using Android” in the National Level paper presentation event PATRIKA. Presented a paper on Yashaswini.
    [Show full text]